Cable management in rack systems

ABSTRACT

A rack system includes one or more racks each configured to receive at least one distribution module. Each rack includes management sections located at the front of the rack; troughs located at the rear of the rack; horizontal channels extending between the management sections and the trough; a storage area located at a first of opposing sides of the rack; a front vertical channel that connects to the storage area and at least some of the management sections; and a travel channel at the rear of the first rack that connects the storage area to the troughs.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of application Ser. No. 14/477,455,filed Sep. 4, 2014, which is a continuation of application Ser. No.13/295,742, filed Nov. 14, 2011, now U.S. Pat. No. 8,842,445, whichapplication claims the benefit of U.S. Provisional Application No.61/413,856, filed Nov. 15, 2010 and U.S. Provisional Application No.61/466,696, filed Mar. 23, 2011, which applications are incorporatedherein by reference in their entirety.

BACKGROUND

In communications infrastructure installations, a variety ofcommunications devices can be used for switching or connecting (e.g.,cross-connecting and/or interconnecting) communications signaltransmission paths in a communications network. For example, somecommunications equipment can be mounted to one of a number of frameworkstructures (e.g., cabinets or racks).

A vast number of cables are run from, to, and between the equipmentmounted to the framework structures. For example, some racks can includedistribution areas at which adapters or other couplers can be installed.Cables can extend from the adapters to various pieces of fiber opticequipment. Using patch cords or cables between the adapters, the piecesof optical equipment can be connected through the rack system.

SUMMARY

The present disclosure relates to rack systems including one or moreracks that have cable termination locations, cable routing locations,and cable management locations to facilitate connecting distributionmodules installed on the rack system. Certain types of rack systemsinclude structure to aid in organizing, routing, and/or protecting thecables. In various implementations, distribution cables, patch cables,and/or additional cables can be routed throughout the rack system.

A variety of examples of desirable product features or methods are setforth in part in the description that follows, and in part will beapparent from the description, or may be learned by practicing variousaspects of the disclosure. The aspects of the disclosure may relate toindividual features as well as combinations of features. It is to beunderstood that both the foregoing general description and the followingdetailed description are explanatory only, and are not restrictive ofthe claimed invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of the description, illustrate several aspects of the presentdisclosure. A brief description of the drawings is as follows:

FIG. 1 is a diagram of a portion of an example communications and datamanagement system in accordance with aspects of the present disclosure;

FIG. 2 is a block diagram of one implementation of a communicationsmanagement system that includes PLI functionality as well as PLMfunctionality in accordance with aspects of the present disclosure;

FIG. 3 is a block diagram of one high-level example of a coupler andmedia reading interface that are suitable for use in the managementsystem of FIG. 2 in accordance with aspects of the present disclosure;

FIG. 4 is a front, perspective view of an example rack suitable for usein a rack system configured in accordance with the principles of thepresent disclosure;

FIG. 5 is a rear, perspective view of the example rack of FIG. 4 inaccordance with the principles of the present disclosure;

FIG. 6 is a front view of the example rack of FIG. 4 in accordance withthe principles of the present disclosure;

FIGS. 7 and 8 are side elevational views of the example rack of FIG. 4in accordance with the principles of the present disclosure;

FIG. 9 is a front, perspective view of an example distribution modulesuitable for mounting to the rack of FIGS. 4-8;

FIG. 10 is a front, perspective view of the example distribution moduleof FIG. 9 with portions of the chassis housing and some of the couplermodules removed for ease in viewing the backplane of the distributionmodule;

FIG. 11 is a front, perspective view of an example passive couplermodule;

FIG. 12 is a cross-sectional view of an example implementation of asmart coupler configured to optically couple together LC-type opticalconnectors;

FIG. 13 is an exploded view of an example implementation of a smartcoupler configured to optically couple together MPO-type opticalconnectors;

FIG. 14 illustrates an example “smart” media segment implemented as anLC-type optical connector;

FIG. 15 illustrates an example “smart” media segment implemented as anMPO-type optical connector;

FIG. 16 is a front elevational view of a portion of the example rack ofFIGS. 4-8 with two distribution modules mounted to the rack;

FIG. 17 is a front, perspective view of a top of the rack of FIG. 16with the two distribution modules visible;

FIG. 18 is a rear elevational view of the portion of the example rack ofFIG. 16 where the rear of the two distribution modules is visible;

FIG. 19 is a rear, perspective view of the rack of FIG. 18 with the twodistribution modules visible;

FIG. 20 is a top plan view of the rack of FIGS. 16-19 with a top bracingbar removed so that the top horizontal tracks are fully visible;

FIG. 21 is an enlarged view of a portion of the rack shown in FIG. 19 inwhich retention members of the distribution modules are more clearlyvisible and in which distribution cables are routed;

FIG. 22 is an enlarged view of a portion of the distribution moduleshown in FIG. 21 with two distribution cables plugged into a rear of thedistribution modules;

FIG. 23 is an enlarged view of a portion of FIG. 6 with representativepatch cables shown routed through the management sections of the rack;

FIGS. 24 and 25 are top plan views of the rack of FIGS. 4-8 withrepresentative patch cables shown routed through the horizontal tracksand over the troughs of the rack;

FIG. 26 is an enlarged view of a portion of FIG. 7 with tworepresentative cables routed from the travel section of the rack,through a storage section, to management sections of the rack;

FIG. 27 is a rear view of a portion of an example rack in whichdistribution cables, patch cables, and PLI cables are routed throughchannels at the rear of the rack in accordance with the principles ofthe present disclosure;

FIG. 28 is an enlarged view of an example master processor of adistribution module with PLI cable routed thereto in accordance with theprinciples of the present disclosure;

FIG. 29 is a plan view of an example rack showing an example couplermodule moving from a retracted position, to a first extended position,and to a second extended position in accordance with the principles ofthe present disclosure; and

FIG. 30 is a partial front, perspective view of the rack of FIG. 4 withtwo example distribution modules mounted thereto.

DETAILED DESCRIPTION

The present disclosure is directed to rack systems that include one ormore racks. Each rack is configured to receive one or more distributionmodules. Each distribution module includes a plurality of patch cableports at which terminated ends of patch cables can be plugged. Anopposite terminated end of each patch cable can be routed to anotherdistribution module or other equipment at the same or a different rackin the rack system.

Each distribution module also includes one or more distribution cableports at which terminated ends of distribution cables can be plugged.Opposite ends of the distribution cables can connect the distributionmodules to a larger communications network as will be described in moredetail herein. Communications signals pass through the distributionmodules between the distribution cables and the patch cables.

Additional cables (e.g., PLI cables) also may be routed to thedistribution modules of the rack systems. In accordance with someaspects, the PLI cables may provide power (e.g., electrical power) tothe distribution modules. In accordance with other aspects, the PLIcables may carry additional data signals between the distributionmodules and a data network as will be described in more detail herein.In certain implementations, the data network is different from thecommunications network to which the distribution cables connect.

The racks of the rack systems include cable management locations andstructure to aid in organizing, routing, and/or protecting the patchcables, distribution cables, and/or PLI cables.

As the term is used herein, a “cable” refers to a physical medium thatis capable of carrying one or more data signals along its length.Non-limiting examples of suitable cables include fiber cables,electrical cables, and hybrid cables. For example, a fiber optic cableincludes one or more optical fibers that are configured to carry opticalsignals along their length. The fibers in a fiber optic cable may bebuffered and/or jacketed (e.g., individually or as a group). Certaintypes of fiber optic cables may be terminated with one or moreconnectors (e.g., SC, LC, FC, LX.5, or MPO connectors).

An electrical cable includes one or more conductors (e.g., wires) thatare configured to carry electrical signals along their length. Theconductors in an electrical cable may be insulated (e.g., individuallyor as a group). Non-limiting examples of electrical cables includeCAT-5, 6, and 7 twisted-pair cables, DS1 line, and DS3 line. Certaintypes of electrical cables may be terminated with one or more connectorsor connector assemblies (e.g., RJ jacks and plugs, DSX jacks and plugs,BNC connectors, F connectors, punch-down terminations, or bantam jacksand plugs). A hybrid cable includes a combination of one or more wiresand one or more optical fibers that may be insulated/jacketed.

Reference will now be made in detail to exemplary aspects of the presentdisclosure that are illustrated in the accompanying drawings. Whereverpossible, the same reference numbers will be used throughout thedrawings to refer to the same or like parts.

FIG. 1 is a diagram of a portion of an example communications and datamanagement system 100. The example system 100 shown in FIG. 1 includes apart of a communications network 101 along which communications signalsS1 pass. In one example implementation, the network 101 can include anInternet Protocol network. In other implementations, however, thecommunications network 101 may include other types of networks.

The communications network 101 includes interconnected networkcomponents (e.g., connector assemblies, inter-networking devices,internet working devices, servers, outlets, and end user equipment(e.g., computers)). In one example implementation, communicationssignals S1 pass from a computer, to a wall outlet, to a port ofcommunication panel, to a first port of an inter-networking device, outanother port of the inter-networking device, to a port of the same oranother communications panel, to a rack mounted server. In otherimplementations, the communications signals S1 may follow other pathswithin the communications network 101.

The portion of the communications network 101 shown in FIG. 1 includesfirst and second connector assemblies 130, 130′ at which communicationssignals S1 pass from one portion of the communications network 101 toanother portion of the communications network 101. Non-limiting examplesof connector assemblies 130, 130′ include, for example, rack-mountedconnector assemblies (e.g., patch panels, distribution units, and mediaconverters for fiber and copper physical communication media),wall-mounted connector assemblies (e.g., boxes, jacks, outlets, andmedia converters for fiber and copper physical communication media), andinter-networking devices (e.g., switches, routers, hubs, repeaters,gateways, and access points).

In the example shown, the first connector assembly 130 defines at leastone port 132 configured to communicatively couple at least a first mediasegment (e.g., cable) 105 to at least a second media segment (e.g.,cable) 115 to enable the communication signals S1 to pass between themedia segments 105, 115. The at least one port 132 of the firstconnector assembly 130 may be directly connected to a port 132′ of thesecond connector assembly 130′. As the term is used herein, the port 132is directly connected to the port 132′ when the communications signalsS1 pass between the two ports 132, 132′ without passing through anintermediate port. For example, plugging a first terminated end of apatch cable into the port 132 and a second terminated end of the patchcable into the port 132′ directly connects the ports 132, 132′.

The port 132 of the first connector assembly 130 also may be indirectlyconnected to the port 132′ of the second connector assembly 130′. As theterm is used herein, the port 132 is indirectly connected to the port132′ when the communications signals S1 pass through an intermediateport when traveling between the ports 132, 132′. For example, in oneimplementation, the communications signals S1 may be routed over onemedia segment from the port 132 at the first connector assembly 130, toa port of a third connector assembly at which the media segment iscoupled, to another media segment that is routed from the port of thethird connector assembly to the port 132′ of the second connectorassembly 130′.

Non-limiting examples of media segments include optical cables,electrical cables, and hybrid cables. The media segments may beterminated with electrical plugs, electrical jacks, fiber opticconnectors, fiber optic adapters, media converters, or other terminationcomponents. In the example shown, each media segment 105, 115 isterminated at a plug or connector 110, 120, respectively, which isconfigured to communicatively connect the media segments 105, 115. Forexample, in one implementation, the port 132 of the connector assembly130 can be configured to align ferrules of two fiber optic connectors110, 120. In another implementation, the port 132 of the connectorassembly 130 can be configured to electrically connect an electricalplug with an electrical socket (e.g., a jack). In yet anotherimplementation, the port 132 can include a media converter configured toconnect an optical fiber to an electrical conductor.

In accordance with some aspects, the connector assembly 130 does notactively manage (e.g., is passive with respect to) the communicationssignals S1 passing through port 132. For example, in someimplementations, the connector assembly 130 does not modify thecommunications signal S1 carried over the media segments 105, 115.Further, in some implementations, the connector assembly 130 does notread, store, or analyze the communications signal S1 carried over themedia segments 105, 115.

In accordance with aspects of the disclosure, the communications anddata management system 100 also provides physical layer information(PLI) functionality as well as physical layer management (PLM)functionality. As the term is used herein, “PLI functionality” refers tothe ability of a physical component or system to identify or otherwiseassociate physical layer information with some or all of the physicalcomponents used to implement the physical layer of the system. As theterm is used herein, “PLM functionality” refers to the ability of acomponent or system to manipulate or to enable others to manipulate thephysical components used to implement the physical layer of the system(e.g., to track what is connected to each component, to traceconnections that are made using the components, or to provide visualindications to a user at a selected component).

As the term is used herein, “physical layer information” refers toinformation about the identity, attributes, and/or status of thephysical components used to implement the physical layer of thecommunications system 100. In accordance with some aspects, physicallayer information of the communications system 100 can include mediainformation, device information, and location information.

As the term is used herein, “media information” refers to physical layerinformation pertaining to cables, plugs, connectors, and other suchphysical media. In accordance with some aspects, the media informationis stored on or in the physical media, themselves. In accordance withother aspects, the media information can be stored at one or more datarepositories for the communications system, either alternatively or inaddition to the media, themselves.

Non-limiting examples of media information include a part number, aserial number, a plug or other connector type, a conductor or fibertype, a cable or fiber length, cable polarity, a cable or fiberpass-through capacity, a date of manufacture, a manufacturing lotnumber, information about one or more visual attributes of physicalcommunication media (e.g., information about the color or shape of thephysical communication media or an image of the physical communicationmedia), and an insertion count (i.e., a record of the number of timesthe media segment has been connected to another media segment or networkcomponent). Media information also can include testing or media qualityor performance information. The testing or media quality or performanceinformation, for example, can be the results of testing that isperformed when a particular segment of media is manufactured.

As the term is used herein, “device information” refers to physicallayer information pertaining to the communications panels,inter-networking devices, media converters, computers, servers, walloutlets, and other physical communications devices to which the mediasegments attach. In accordance with some aspects, the device informationis stored on or in the devices, themselves. In accordance with otheraspects, the device information can be stored at one or more datarepositories for the communications system, either alternatively or inaddition to the devices, themselves. In accordance with still otheraspects, the device information can be stored in the media segmentsattached thereto. Non-limiting examples of device information include adevice identifier, part number, model number, catalogue number, a devicetype, date of manufacture, insertion counts, port priority data (thatassociates a priority level with each port), and port updates (describedin more detail herein).

As the term is used herein, “location information” refers to physicallayer information pertaining to a physical layout of a building orbuildings in which the network 101 is deployed. Location informationalso can include information indicating where each communicationsdevice, media segment, network component, or other component isphysically located within the building. In accordance with some aspects,the location information of each system component is stored on or in therespective component. In accordance with other aspects, the locationinformation can be stored at one or more data repositories for thecommunications system, either alternatively or in addition to the systemcomponents, themselves.

In accordance with some aspects, one or more of the components of thecommunications network 101 are configured to store physical layerinformation pertaining to the component as will be disclosed in moredetail herein. In FIG. 1, the connectors 110, 120, the media segments105, 115, and/or the connector assemblies 130, 130′ may store physicallayer information. For example, in FIG. 1, each connector 110, 120 maystore information pertaining to itself (e.g., type of connector, data ofmanufacture, etc.) and/or to the respective media segment 105, 115(e.g., type of media, test results, etc.).

In another example implementation, the media segments 105, 115 orconnectors 110, 120 may store media information that includes a count ofthe number of times that the media segment (or connector) has beeninserted into port 132. In such an example, the count stored in or onthe media segment is updated each time the segment (or plug orconnector) is inserted into port 132. This insertion count value can beused, for example, for warranty purposes (e.g., to determine if theconnector has been inserted more than the number of times specified inthe warranty) or for security purposes (e.g., to detect unauthorizedinsertions of the physical communication media).

One or more of the components of the communications network 101 can readthe physical layer information from one or more media segments retainedthereat. In certain implementations, one or more network componentsincludes a media reading interface that is configured to read physicallayer information stored on or in the media segments or connectorsattached thereto. For example, in one implementation, the connectorassembly 130 includes a media reading interface 134 that can read mediainformation stored on the media cables 105, 115 retained within the port132. In another implementation, the media reading interface 134 can readmedia information stored on the connectors or plugs 110, 120 terminatingthe cables 105, 115, respectively.

In accordance with some aspects of the disclosure, the physical layerinformation read by a network component may be processed or stored atthe component. For example, in certain implementations, the firstconnector assembly 130 shown in FIG. 1 is configured to read physicallayer information stored on the connectors 110, 120 and/or on the mediasegments 105, 115 using media reading interface 134. Accordingly, inFIG. 1, the first connector assembly 130 may store not only physicallayer information about itself (e.g., the total number of availableports at that assembly 130, the number of ports currently in use, etc.),but also physical layer information about the connectors 110, 120inserted at the ports and/or about the media segments 105, 115 attachedto the connectors 110, 120.

The physical layer information obtained by the media reading interfacemay be communicated (see PLI signals S2) over the network 101 forprocessing and/or storage. In accordance with some aspects, thecommunications network 101 includes a data network (e.g., see network218 of FIG. 2) along which the physical layer information iscommunicated. At least some of the media segments and other componentsof the data network may be separate from those of the communicationsnetwork 101 to which such physical layer information pertains. Forexample, in some implementations, the first connector assembly 130 mayinclude a plurality of “normal” ports (e.g., fiber optic adapter ports)at which connectorized media segments (e.g., optical fibers) are coupledtogether to create a path for communications signals S1. The firstconnector assembly 130 also may include one or more PLI ports 136 atwhich the physical layer information (see PLI signals S2) are passed tocomponents of the data network (e.g., to one or more aggregation points150 and/or to one or more computer systems 160).

In other implementations, however, the physical layer information may becommunicated over the communications network 101 just like any othersignal, while at the same time not affecting the communication signalsS1 that pass through the connector assembly 130 on the normal ports 132.Indeed, in some implementations, the physical layer information may becommunicated as one or more of the communication signals S1 that passthrough the normal ports 132 of the connector assemblies 130, 130′. Forexample, in one implementation, a media segment may be routed betweenthe PLI port 136 and one of the “normal” ports 132. In anotherimplementation, the media segment may be routed between the PLI port 136and a “normal” port of another connector assembly. In suchimplementations, the physical layer information may be passed along thecommunications network 101 to other components of the communicationsnetwork 101 (e.g., to another connector assembly, to one or moreaggregation points 150 and/or to one or more computer systems 160). Byusing the network 101 to communicate physical layer informationpertaining to it, an entirely separate data network need not be providedand maintained in order to communicate such physical layer information.

For example, in the implementation shown in FIG. 1, each connectorassembly 130 includes at least one PLI port 136 that is separate fromthe “normal” ports 132 of the connector assembly 130. Physical layerinformation is communicated between the connector assembly 130 and thecommunications network 101 through the PLI port 136. Components of thecommunications network 101 may be connected to one or more aggregationdevices 150 and/or to one or more computing systems 160. In the exampleshown in FIG. 1, the connector assembly 130 is connected to arepresentative aggregation device 150, a representative computing system160, and to other components of the network 101 (see looped arrows) viathe PLI port 136.

In some implementations, some types of physical layer informationpertaining to media segments can be obtained by the connector assembly130 from a user at the connector assembly 130 via a user interface(e.g., a keypad, a scanner, a touch screen, buttons, etc.). For example,physical layer information pertaining to media that is not configured tostore such information can be entered manually into the connectorassembly 130 by the user. In certain implementations, the connectorassembly 130 can provide the physical layer information obtained fromthe user to other devices or systems that are coupled to thecommunications network 101 and/or a separate data network.

In other implementations, some or all physical layer information can beobtained by the connector assembly 130 from other devices or systemsthat are coupled to the communications network 101 and/or a separatedata network. For example, physical layer information pertaining tomedia that is not configured to store such information can be enteredmanually into another device or system (e.g., at the connector assembly130, at the computer 160, or at the aggregation point 150) that iscoupled to the network 101 and/or a separate data network.

In some implementations, some types of non-physical layer information(e.g., network information) also can be obtained by one networkcomponent (e.g., a connector assembly 130, an aggregation point 150, ora computer 160) from other devices or systems that are coupled to thecommunications network 101 and/or a separate data network. For example,the connector assembly 130 may pull non-physical layer information fromone or more components of the network 101. In other implementations, thenon-physical layer information can be obtained by the connector assembly130 from a user at the connector assembly 130.

In some implementations, the connector assembly 130 is configured tomodify (e.g., add, delete, and/or change) the physical layer informationstored in or on the segment of physical communication media 105, 115(i.e., or the associated connectors 110, 120). For example, in someimplementations, the media information stored in or on the segment ofphysical communication media 105, 115 can be updated to include theresults of testing that is performed when a segment of physical media isinstalled or otherwise checked. In other implementations, such testinginformation is supplied to the aggregation point 150 for storage and/orprocessing. The modification of the physical layer information does notaffect the communications signals S1 passing through the connectorassembly 130.

FIG. 2 is a block diagram of one example implementation of acommunications management system 200 that includes PLI functionality aswell as PLM functionality. The management system 200 comprises aplurality of connector assemblies 202. The management system 200includes one or more connector assemblies 202 connected to an IP network218. The connector assemblies 202 shown in FIG. 2 illustrate variousexample implementations of the connector assemblies 130, 130′ of FIG. 1.

Each connector assembly 202 includes one or more ports 204, each ofwhich is used to connect two or more segments of physical communicationmedia to one another (e.g., to implement a portion of a logicalcommunication link for communication signals S1 of FIG. 1). At leastsome of the connector assemblies 202 are designed for use with segmentsof physical communication media that have physical layer informationstored in or on them. The physical layer information is stored in or onthe segment of physical communication media in a manner that enables thestored information, when the segment is attached to a port 204, to beread by a programmable processor 206 associated with the connectorassembly 202.

Each programmable processor 206 is configured to execute software orfirmware that causes the programmable processor 206 to carry out variousfunctions described below. Each programmable processor 206 also includessuitable memory (not shown) that is coupled to the programmableprocessor 206 for storing program instructions and data. In general, theprogrammable processor 206 determines if a physical communication mediasegment is attached to a port 204 with which that processor 206 isassociated and, if one is, to read the identifier and attributeinformation stored in or on the attached physical communication mediasegment (if the segment includes such information stored therein orthereon) using the associated media reading interface 208.

In some implementations, each of the ports 204 of the connectorassemblies 202 comprises a respective media reading interface 208 viawhich the respective programmable processor 206 is able to determine ifa physical communication media segment is attached to that port 204 and,if one is, to read the physical layer information stored in or on theattached segment (if such media information is stored therein orthereon). In other implementations, a single media reading interface 208may correspond to two or more ports 204. The programmable processor 206associated with each connector assembly 202 is communicatively coupledto each of the media reading interfaces 208 using a suitable bus orother interconnect (not shown).

In FIG. 2, four example types of connector assembly configurations 210,212, 214, and 215 are shown. In the first connector assemblyconfiguration 210 shown in FIG. 2, each connector assembly 202 includesits own respective programmable processor 206 and its own respectivenetwork interface 216 that is used to communicatively couple thatconnector assembly 202 to an Internet Protocol (IP) network 218. In someimplementations, the ports 204 of the connector assemblies 202 alsoconnect to the IP network 218. In other implementations, however, onlythe network interfaces 216 couple to the IP network 218.

In the second type of connector assembly configuration 212, a group ofconnector assemblies 202 are physically located near each other (e.g.,in a rack, rack system, or equipment closet). Each of the connectorassemblies 202 in the group includes its own respective programmableprocessor 206. However, in the second connector assembly configuration212, some of the connector assemblies 202 (referred to here as“interfaced connector assemblies”) include their own respective networkinterfaces 216 while some of the connector assemblies 202 (referred tohere as “non-interfaced connector assemblies”) do not. Thenon-interfaced connector assemblies 202 are communicatively coupled toone or more of the interfaced connector assemblies 202 in the group vialocal connections. In this way, the non-interfaced connector assemblies202 are communicatively coupled to the IP network 218 via the networkinterface 216 included in one or more of the interfaced connectorassemblies 202 in the group. In the second type of connector assemblyconfiguration 212, the total number of network interfaces 216 used tocouple the connector assemblies 202 to the IP network 218 can bereduced. Moreover, in the particular implementation shown in FIG. 2, thenon-interfaced connector assemblies 202 are connected to the interfacedconnector assembly 202 using a daisy chain topology (though othertopologies can be used in other implementations and embodiments).

In the third type of connector assembly configuration 214, a group ofconnector assemblies 202 are physically located near each other (e.g.,within a rack, rack system, or equipment closet). Some of the connectorassemblies 202 in the group (also referred to here as “master” connectorassemblies 202) include both their own programmable processors 206 andnetwork interfaces 216, while some of the connector assemblies 202 (alsoreferred to here as “slave” connector assemblies 202) do not includetheir own programmable processors 206 or network interfaces 216. Each ofthe slave connector assemblies 202 is communicatively coupled to one ormore of the master connector assemblies 202 in the group via one or morelocal connections. The programmable processor 206 in each of the masterconnector assemblies 202 is able to carry out the PLM functions for boththe master connector assembly 202 of which it is a part and any slaveconnector assemblies 202 to which the master connector assembly 202 isconnected via the local connections. As a result, the cost associatedwith the slave connector assemblies 202 can be reduced. In theparticular implementation shown in FIG. 2, the slave connectorassemblies 202 are connected to a master connector assembly 202 in astar topology (though other topologies can be used in otherimplementations and embodiments).

In the fourth type of connector assembly configuration 215, a group ofconnector assemblies (e.g., distribution modules) 202 are housed withina common chassis or other enclosure. Each of the connector assemblies202 in the configuration 215 includes their own programmable processors206. In the context of this configuration 215, the programmableprocessors 206 in the connector assemblies 202 are “slave” processors206. Each of the slave programmable processors 206 in the group iscommunicatively coupled to a common “master” programmable processor 217(e.g., over a backplane included in the chassis or enclosure). Themaster programmable processor 217 is coupled to a network interface 216that is used to communicatively couple the master programmable processor217 to the IP network 218.

In the fourth configuration 215, each slave programmable processor 206is configured to manage the media reading interfaces 208 to determine ifphysical communication media segments are attached to the port 204 andto read the physical layer information stored in or on the attachedphysical communication media segments (if the attached segments havesuch information stored therein or thereon). The physical layerinformation is communicated from the slave programmable processor 206 ineach of the connector assemblies 202 in the chassis to the masterprocessor 217. The master processor 217 is configured to handle theprocessing associated with communicating the physical layer informationread from by the slave processors 206 to devices that are coupled to theIP network 218.

In accordance with some aspects, the communications management system200 includes functionality that enables the physical layer informationcaptured by the connector assemblies 202 to be used by application-layerfunctionality outside of the traditional physical-layer managementapplication domain. That is, the physical layer information is notretained in a PLM “island” used only for PLM purposes but is insteadmade available to other applications. For example, in the particularimplementation shown in FIG. 2, the management system 200 includes anaggregation point 220 that is communicatively coupled to the connectorassemblies 202 via the IP network 218.

The aggregation point 220 includes functionality that obtains physicallayer information from the connector assemblies 202 (and other devices)and stores the physical layer information in a data store. Theaggregation point 220 can be used to receive physical layer informationfrom various types of connector assemblies 202 that have functionalityfor automatically reading information stored in or on the segment ofphysical communication media. Also, the aggregation point 220 andaggregation functionality 224 can be used to receive physical layerinformation from other types of devices that have functionality forautomatically reading information stored in or on the segment ofphysical communication media. Examples of such devices include end-userdevices—such as computers, peripherals (e.g., printers, copiers, storagedevices, and scanners), and IP telephones—that include functionality forautomatically reading information stored in or on the segment ofphysical communication media.

The aggregation point 220 also can be used to obtain other types ofphysical layer information. For example, in this implementation, theaggregation point 220 also obtains information about physicalcommunication media segments that is not otherwise automaticallycommunicated to an aggregation point 220. This information can beprovided to the aggregation point 220, for example, by manually enteringsuch information into a file (e.g., a spreadsheet) and then uploadingthe file to the aggregation point 220 (e.g., using a web browser) inconnection with the initial installation of each of the various items.Such information can also, for example, be directly entered using a userinterface provided by the aggregation point 220 (e.g., using a webbrowser).

The aggregation point 220 also includes functionality that provides aninterface for external devices or entities to access the physical layerinformation maintained by the aggregation point 220. This access caninclude retrieving information from the aggregation point 220 as well assupplying information to the aggregation point 220. In thisimplementation, the aggregation point 220 is implemented as “middleware”that is able to provide such external devices and entities withtransparent and convenient access to the PLI maintained by the accesspoint 220. Because the aggregation point 220 aggregates PLI from therelevant devices on the IP network 218 and provides external devices andentities with access to such PLI, the external devices and entities donot need to individually interact with all of the devices in the IPnetwork 218 that provide PLI, nor do such devices need to have thecapacity to respond to requests from such external devices and entities.

For example, as shown in FIG. 2, a network management system (NMS) 230includes PLI functionality 232 that is configured to retrieve physicallayer information from the aggregation point 220 and provide it to theother parts of the NMS 230 for use thereby. The NMS 230 uses theretrieved physical layer information to perform one or more networkmanagement functions. In certain implementations, the NMS 230communicates with the aggregation point 220 over the IP network 218. Inother implementations, the NMS 230 may be directly connected to theaggregation point 220.

As shown in FIG. 2, an application 234 executing on a computer 236 alsocan use the API implemented by the aggregation point 220 to access thePLI information maintained by the aggregation point 220 (e.g., toretrieve such information from the aggregation point 220 and/or tosupply such information to the aggregation point 220). The computer 236is coupled to the IP network 218 and accesses the aggregation point 220over the IP network 218.

In the example shown in FIG. 2, one or more inter-networking devices 238used to implement the IP network 218 include physical layer information(PLI) functionality 240. The PLI functionality 240 of theinter-networking device 238 is configured to retrieve physical layerinformation from the aggregation point 220 and use the retrievedphysical layer information to perform one or more inter-networkingfunctions. Examples of inter-networking functions include Layer 1, Layer2, and Layer 3 (of the OSI model) inter-networking functions such as therouting, switching, repeating, bridging, and grooming of communicationtraffic that is received at the inter-networking device.

The aggregation point 220 can be implemented on a standalone networknode (e.g., a standalone computer running appropriate software) or canbe integrated along with other network functionality (e.g., integratedwith an element management system or network management system or othernetwork server or network element). Moreover, the functionality of theaggregation point 220 can be distribute across many nodes and devices inthe network and/or implemented, for example, in a hierarchical manner(e.g., with many levels of aggregation points). The IP network 218 caninclude one or more local area networks and/or wide area networks (e.g.,the Internet). As a result, the aggregation point 220, NMS 230, andcomputer 236 need not be located at the same site as each other or atthe same site as the connector assemblies 202 or the inter-networkingdevices 238.

Also, power can be supplied to the connector assemblies 202 usingconventional “Power over Ethernet” techniques specified in the IEEE802.3af standard, which is hereby incorporated herein by reference. Insuch an implementation, a power hub 242 or other power supplying device(located near or incorporated into an inter-networking device that iscoupled to each connector assembly 202) injects DC power onto one ormore power cables (e.g., a power wire included in a copper twisted-paircable) used to connect each connector assembly 202 to the IP network218. In other implementations, power may be provided using “Power overEthernet Plug” techniques specified in the IEEE 802.3at standard, whichis hereby incorporated herein by reference.

FIG. 3 is a schematic diagram of one example connection system 1800including a connector assembly 1810 configured to collect physical layerinformation from at least one segment of physical communications media.The example connector assembly 1810 of FIG. 3 is configured to connectsegments of optical physical communications media in a physical layermanagement system. The connector assembly 1810 includes a fiber opticadapter defining at least one connection opening 1811 having a firstport end 1812 and a second port end 1814. A sleeve (e.g., a splitsleeve) 1803 is arranged within the connection opening 1811 of theadapter 1810 between the first and second port ends 1812, 1814. Eachport end 1812, 1814 is configured to receive a connector arrangement aswill be described in more detail herein.

A first example segment of optical physical communication media includesa first optical fiber 1822 terminated by a first connector arrangement1820. A second example segment of optical physical communication mediaincludes a second optical fiber 1832 terminated by a second connectorarrangement 1830. The first connector arrangement 1820 is plugged intothe first port end 1812 and the second connector arrangement 1830 isplugged into the second port end 1814. Each fiber connector arrangement1820, 1830 includes a ferrule 1824, 1834 through which optical signalsfrom the optical fiber 1822, 1832, respectively, pass.

The ferrules 1824, 1834 of the connector arrangements 1820, 1830 arealigned by the sleeve 1803 when the connector arrangements 1820, 1830are inserted into the connection opening 1811 of the adapter 1810.Aligning the ferrules 1824, 1834 provides optical coupling between theoptical fibers 1822, 1832. In some implementations, each segment ofoptical physical communication media (e.g., each optical fiber 1822,1832) carries communication signals (e.g., communications signals S1 ofFIG. 1). The aligned ferrules 1824, 1834 of the connector arrangements1820, 1830 create an optical path along which the communication signals(e.g., signals S1 of FIG. 1) may be carried.

In some implementations, the first connector arrangement 1820 mayinclude a storage device 1825 that is configured to store physical layerinformation (e.g., an identifier and/or attribute information)pertaining to the segment of physical communications media (e.g., thefirst connector arrangement 1820 and/or the fiber optic cable 1822terminated thereby). In some implementations, the connector arrangement1830 also includes a storage device 1835 that is configured to storeinformation (e.g., an identifier and/or attribute information)pertaining to the second connector arrangement 1830 and/or the secondoptic cable 1832 terminated thereby.

In one implementation, each of the storage devices 1825, 1835 isimplemented using an EEPROM (e.g., a PCB surface-mount EEPROM). In otherimplementations, the storage devices 1825, 1835 are implemented usingother non-volatile memory device. Each storage device 1825, 1835 isarranged and configured so that it does not interfere or interact withthe communications signals communicated over the media segments 1822,1832.

In accordance with some aspects, the adapter 1810 is coupled to at leasta first media reading interface 1816. In certain implementations, theadapter 1810 also is coupled to at least a second media interface 1818.In some implementations, the adapter 1810 is coupled to multiple mediareading interfaces. In certain implementations, the adapter 1810includes a media reading interface for each port end defined by theadapter 1810. In other implementations, the adapter 1810 includes amedia reading interface for each connection opening 1811 defined by theadapter 1810. In still other implementations, the adapter 1810 includesa media reading interface for each connector arrangement that theadapter 1810 is configured to receive. In still other implementations,the adapter 1810 includes a media reading interface for only a portionof the connector arrangement that the adapter 1810 is configured toreceive.

In some implementations, at least the first media reading interface 1816is mounted to a printed circuit board 1815. In the example shown, thefirst media reading interface 1816 of the printed circuit board 1815 isassociated with the first port end 1812 of the adapter 1810. In someimplementations, the printed circuit board 1815 also can include thesecond media reading interface 1818. In one such implementation, thesecond media reading interface 1818 is associated with the second portend 1814 of the adapter 1810.

The printed circuit board 1815 of the connector assembly 1810 can becommunicatively connected to one or more programmable processors (e.g.,processors 216 of FIG. 2) and/or to one or more network interfaces(e.g., network interfaces 216 of FIG. 2). The network interface may beconfigured to send the physical layer information (e.g., see signals S2of FIG. 1) to a physical layer management network (e.g., seecommunications network 101 of FIG. 1 or IP network 218 of FIG. 2). Inone implementation, one or more such processors and interfaces can bearranged as components on the printed circuit board 1815. In anotherimplementation, one or more such processor and interfaces can bearranged on separate circuit boards that are coupled together. Forexample, the printed circuit board 1815 can couple to other circuitboards via a card edge type connection, a connector-to-connector typeconnection, a cable connection, etc.

When the first connector arrangement 1820 is received in the first portend 1812 of the adapter 1810, the first media reading interface 1816 isconfigured to enable reading (e.g., by the processor) of the informationstored in the storage device 1825. The information read from the firstconnector arrangement 1820 can be transferred through the printedcircuit board 1815 to a physical layer management network, e.g., network101 of FIG. 1, network 218 of FIG. 2, etc. When the second connectorarrangement 1830 is received in the second port end 1814 of the adapter1810, the second media reading interface 1818 is configured to enablereading (e.g., by the processor) of the information stored in thestorage device 1835. The information read from the second connectorarrangement 1830 can be transferred through the printed circuit board1815 or another circuit board to the physical layer management network.

In some such implementations, the storage devices 1825, 1835 and themedia reading interfaces 1816, 1818 each comprise three (3) leads—apower lead, a ground lead, and a data lead. The three leads of thestorage devices 1825, 1835 come into electrical contact with three (3)corresponding leads of the media reading interfaces 1816, 1818 when thecorresponding media segment is inserted in the corresponding port. Incertain example implementations, a two-line interface is used with asimple charge pump. In still other implementations, additional leads canbe provided (e.g., for potential future applications). Accordingly, thestorage devices 1825, 1835 and the media reading interfaces 1816, 1818may each include four (4) leads, five (5) leads, six (6) leads, etc.

FIGS. 4-8 show one example rack system 300 on which one or moreconnector assemblies (e.g., distribution modules 400 of FIGS. 9-10) canbe mounted. The example rack system 300 includes a rack 301 having afront 302 (FIG. 4), a rear 303 (FIG. 5), a top 304 (FIG. 6), a bottom305, a first side 306 (FIG. 7), and a second side 307 (FIG. 8).

In certain implementations, the rack system 300 may include two or moreadjacent racks 301. For example, two or more racks 301 may be arrangedin a row with the first side 306 of one rack 301 being located adjacentthe second side 307 of another rack 301. In some implementations, an endcover may be attached to a rack 301 at one or both ends of the row toprotect the exposed sides of the rack 301. For example, an end coverhaving a U-shaped transverse cross-section may extend from the bottom ofthe rack 301 to the top of the rack 301 across the exposed side 306, 307of the rack 301.

Each rack 301 defines one or more distribution sections 308 (FIG. 6).Each distribution section 308 includes a mounting area 320 at which oneor more distribution modules 400 can be installed. Each distributionmodule 400 includes a plurality of front ports 422 coupled to at leastone rear port 424 (e.g., see FIG. 10). In the example shown, thedistribution module 400 includes a chassis housing 410 in which one ormore coupler modules 420 are installed. Each coupler module 420 includesat least a first set of couplers 421 (FIG. 10) that define the frontcable ports 422.

Patch cables 510 are routed between distribution modules 400 on theracks 301. For example, a first terminated end 512 (e.g., see FIG. 23)of each patch cable 510 may be plugged into a first front port 422 of adistribution module 400 and a second terminated end 514 (e.g., see FIG.23) of each patch cable 510 may be plugged into a second front port 422of the same or a different distribution module 400. Each distributionsection 308 of the rack 301 is associated with one or more cablemanagement sections 330 (FIG. 4) for managing the patch cables 510, oneor more travel sections 350 (FIG. 5) along which the patch cables 510can be routed within and/or between racks 301, and one or more tracks380 (FIGS. 17, 24, and 25) along which the patch cables 510 can berouted between the management sections 330 and the travel sections 350.

Distribution cables 520 are routed (e.g., via cable raceways) betweenthe distribution modules 400 and a communications network (e.g.,communications network 101 of FIG. 1 and/or IP network 218 of FIG. 2).For example, a terminated end 522 of each distribution cable 520 may beplugged into a rear port 424 of the distribution module 400 (e.g., seeFIG. 22). The opposite ends of the distribution cables 520 couple (e.g.,via connectors, optical splices, etc.) with components of thecommunications network. The racks 301 include one or more vertical cableguides/channels 374 (FIGS. 18 and 20) along which the distributioncables 520 may be routed between the distribution modules 400 and thecable raceways or other routing structures.

PLI cables (e.g., power and/or data cables) 530 also may be routed(e.g., via cable raceways) between the distribution modules 400 and adata network (e.g., communications network 101 of FIG. 1 and/or IPnetwork 218 of FIG. 2). For example, a terminated end 532 of each PLIcable 530 may be plugged into a PLI port 428 of the distribution module400 (e.g., see FIG. 28). The opposite ends of the PLI cables 530 couple(e.g., via connectors, optical splices, etc.) with components of thedata network. In certain implementations, the data network shares atleast some components with the communications network. In certainimplementations, the racks 301 also include additional vertical cableguides/channels 375 (FIGS. 18 and 20) along which the PLI cables 530 maybe routed between the distribution modules 400 and the cable raceways orother routing structures.

In some implementations, grounding cables also may be routed (e.g., viacable raceways) to the distribution modules 400. For example, an end ofeach grounding cable may be connected to a grounding plate or groundingport of the distribution module 400 (e.g., see FIGS. 10 and 19). Theopposite ends of the grounding cables may be routed to a grounding bar(e.g., located at the top of the rack 301). In some implementations, thegrounding cables are routed from the grounding bar through theadditional vertical cable guides/channels 375 (FIGS. 18 and 20), to thedistribution modules 400. In certain implementations, the a group of PLIcables are routed down a first of the additional vertical cable channels375 and a group of grounding cables are routed down a second of theadditional vertical cable channels 375.

The bottom 305 of the rack 301 includes a base 309 (FIG. 4). In someimplementations, the base 309 is configured to be secured to the ground(e.g., using bolts, screws, rivets, or other fasteners). In certainimplementations, the base 309 is configured to receive distributioncables 520 and/or PLI cables 530 from one or more cable raceways (e.g.,floor-level or below-ground raceways) or other routing structures. Forexample, the base 309 may include cut-outs or openings through which thedistribution cables 520 and/or PLI cables 530 can be routed up toguides/channels 374, 375 at the rear 303 of the rack 301 as will bedescribed in more detail herein.

The rack 301 also includes a frame construction 310 extending upwardlyfrom the base 309 (FIGS. 4 and 5). Certain types of frame constructions310 may be configured to receive distribution cables 520 and/or PLIcables 530 transitioned from overhead cable raceways or other routingstructures. The frame construction 310 of the rack 301 defines and/orsupports the mounting areas 320 (FIG. 6), the cable management sections330 (FIG. 4), the travel sections 350 (FIG. 5), and at least one storagesection 360 (FIGS. 7 and 8) at which slack length of the patch cables510 can be stored. In the example shown, the frame construction includesa first tower 311 and a second tower 313 interconnected by at least onebracing member 314 (FIG. 4).

In some implementations, one or more of the distribution cables 520and/or PLI cables 530 are routed to the rack 301 along raceways. In someimplementations, the cables are routed along overhead raceways connectedto a top 304 of the rack 301. In other implementations, the cables arerouted along floor-level or below-ground raceways connected to thebottom 305 of the rack 301. Such raceways facilitate routing cableswithin a building. For example, the raceways may form a passageway orchannel along which cables may be routed to the rack 301 from a point ofentry into the building. In some implementations, the raceways includeU-shaped troughs along which cables can be routed. In otherimplementations, the raceways include enclosed tubes or covered troughsthrough which the cables are routed.

In some implementations, the travel section 350 is located at the rear303 of the rack 301 (see FIG. 5). In the example shown, the travelsection 350 includes one or more troughs 352 extending across the rear303 of the rack 301 (e.g., between the first and second towers 311,313). At least one of the sides 306, 307 of the rack 301 provides acable slack storage area 360. In certain implementations, both sides306, 307 of the rack 301 provide slack storage areas 360. For example, aside of each tower 311, 313 may define a storage section 360. In otherimplementations, however, the travel and storage sections 350, 360,respectively, may be located on any desired side of the rack 301.

The mounting areas 320 of the rack 301 are configured to position thedistribution modules 400 so that the front ports 422 of the distributionmodules 400 are accessible from the front 302 of the rack 301 (e.g., seeFIG. 17). The management sections 330 are provided at the front 302 ofthe rack 301. For example, in one implementation, the mounting areas 320are provided between the towers 311, 313 (FIG. 4) and the managementsections 330 are provided at the fronts of the towers 311, 313. Incertain implementations, the rear ports 424 of the distribution modules400 are accessible from the rear 303 of the rack 301 (e.g., see FIGS.21-22).

Referring to FIGS. 9-15, each distribution module 400 mounted to therack 301 includes a first side 401 that is accessible from the front 302of the rack 301 and a second side 402 that is accessible from the rear303 of the rack 301 (FIG. 9). One or more cables 500 can be routed toports of the distribution modules 400 to connect the distributionmodules 400 to other distribution modules 400, to a communicationsnetwork (e.g., communications network 101 of FIG. 1 or IP network 218 ofFIG. 2), and/or to a data network (e.g., IP network 218 of FIG. 2 orcommunications network 101 of FIG. 1).

Each distribution module 400 is configured to couple together (e.g.,electrically couple, optically couple, etc.) one or more distributioncables 520 with two or more patch cables 510. In certainimplementations, each of the distribution modules 400 includes one ormore front cable ports 422 at the first side 401 to receive patch cables510 and one or more rear cable ports 424 to receive distribution cables520. In some implementations, a first set of couplers 421 also definesthe rear ports 424 of the distribution modules 400. For example, incertain implementations, distribution cables 520 can be routed withinthe distribution modules 400 from the second sides 402 of thedistribution modules 400 to rear ports 424 defined by the first set ofcouplers 421 to form an optical path between the distribution cables 520and the patch cables 510.

In other implementations, however, certain types of distribution modules400 may include a second set of couplers 423 located at the second side402 of the distribution module 400 (see FIG. 10). The couplers 423 ofthe second set are communicatively coupled to the couplers 421 of thefirst set (e.g., using a hydra cable or other connection cable). Forexample, in some implementations, distribution cables 520 can be routedto the rear ports 424 of the second set of couplers 423 to form anoptical path between the distribution cables 520 and the patch cables510 plugged into the front ports 422 of the first set of couplers 421.

In accordance with some aspects, one or more of the distribution modules400 may be “smart” distribution modules. As the term is used herein, a“smart” distribution module is a distribution module having PLIfunctionality. In some implementations, a smart distribution module 400may include a chassis having a backplane 415 configured to connect to adata network. In such implementations, one or more PLI cable ports 428are provided at the distribution modules 400 to receive the PLI cables530. For example, a chassis processor 430 (FIG. 28), which is connectedto the backplane 415, may be define PLI cable ports 428 for one or morePLI cables 530.

One or more of the coupler modules 420 received at the distributionmodule 400 may be “smart” coupler modules. As the term is used herein, asmart coupler module is a coupler module having PLI functionality.Certain types of smart coupler modules include a circuit boardarrangement 425, a processor 426, and one or more “smart” couplers. A“smart” coupler is a coupler having at least one media reading interfaceconfigured to read physical layer information stored on or in one ormore physical media segments received at the coupler. The processor 426may manage the media reading interfaces via the circuit boardarrangement 425. The circuit board arrangement 425 of each couplermodule is configured to connect the processor 426 to the backplane 415of the distribution module 400. In some implementations, all of thecouplers 421, 423 include media reading interfaces. In otherimplementations, only the front couplers 421 or only the rear couplers423 include media reading interfaces.

A “smart” distribution module 400 may include memory in which physicallayer information pertaining to the distribution module 400 can bestored. For example, the memory may be provided on the chassis processor430. Non-limiting examples of physical layer information pertaining to adistribution module 400 include an indication of the size of thedistribution module 400 (e.g., 1 RU, 2 RU, 3 RU, etc.), a part number, amodel number, a catalogue number, a date of manufacture, an indicationof the number of coupler modules 420 that the distribution module 400 isconfigured to receive.

A “smart” coupler module 420 may include memory in which physical layerinformation pertaining to the coupler module 420 can be stored. Forexample, the memory may be provided on the processor 426. Non-limitingexamples of physical layer information pertaining to a coupler module420 include a part number, a model number, a catalogue number, a date ofmanufacture, a number of available ports, an insertion count for thefront couplers 421 (or ports thereof), an insertion count for the rearcouplers 423 (or ports thereof), and an indication of whether thecoupler module or ports thereon are configured to single mode ormulti-mode.

In accordance with other aspects, one or more of the coupler modules 420positioned at the distribution module 400 may be “passive” couplermodules. As the term is used herein, a “passive” coupler module is acoupler module that does not have PLI functionality. For example, insome implementations, a passive coupler module may have one or more“passive” couplers that do not include media reading interfaces. Incertain implementations, the passive coupler module does not have acircuit board arrangement or a processor (see FIG. 11).

In accordance with some aspects, a passive coupler module may beinstalled at a smart distribution module 400. For example, the passivecoupler module may have the same or similar dimensions of the smartcoupler module to enable the passive coupler module to fit within thesmart distribution module 400. In other implementations, the passivecoupler module may be installed at a “passive” distribution module 400.As the term is used herein, a “passive” distribution module 400 is adistribution module that does not include a backplane or a chassisprocessor. In certain implementations, a smart coupler module may beinstalled at the passive distribution module.

FIGS. 12 and 13 illustrate some example implementations of smartcouplers (e.g., couplers 421 and/or 423). FIG. 12 is a cross-sectionalview of a coupler 421, 423 configured to optically couple togetherLC-type optical connectors. FIG. 13 is an exploded view of a coupler421, 423 configured to optically couple together MPO-type opticalconnectors. Each smart coupler 421, 423 includes one or more mediareading interfaces 427. For example, the smart couplers 421, 423 mayinclude the media reading interfaces 427 within one or morethrough-openings 429 leading from an exterior of the coupler 421, 423 toa through-passage of the coupler 421, 423 (e.g., see FIG. 12).

FIGS. 14 and 15 illustrate some example implementations of “smart” mediasegments 500. As the term is used herein, a “smart” media segment 500 isa media segment having a storage device configured to store physicallayer information. FIG. 14 is a perspective view of an example LC-typeoptical connector 501 having a storage device 505. FIG. 15 is anexploded view of an example MPO-type optical connector 501′ having astorage device 505′. In the examples shown, the storage devices 505,505′ are positioned at keys of the connectors 501, 501′.

The media reading interfaces 427 of the smart couplers 421, 423 arecoupled to the circuit board arrangement 425 of the smart coupler module420. In some implementations, each media reading interface 427determines whether a connectorized end of a media segment 500 has beenreceived at a port of the smart coupler 421, 423. In certainimplementations, each media reading interface 427 may act as a switch tocomplete or break an electrical connection when a media segment isreceived at the coupler. For example, insertion of a fiber opticconnector 501, 501′ into one of the couplers 421, 423 may flex a portionof the media reading interface 427 through the opening 429 towards thecircuit board 426.

In some implementations, each media reading interface 427 of a smartcoupler 421, 423 forms an electrical connection between the storagedevice 505, 505′ of the received connector 501, 501′ and the circuitboard arrangement 425 of the coupler module 420 (see FIG. 12). Byconnecting the storage device 505, 505′ to the circuit board arrangement425, the media reading interface 426 enables the processor 426 of eachcoupler module 420 to read and/or write data to and/or from the storagedevice 505, 505′.

Some example types of smart couplers 421, 423 are disclosed in moredetail in U.S. Provisional Application No. 61/303,961, filed Feb. 12,2010, titled “Fiber Plugs and Adapters for Managed Connectivity,” U.S.Provisional Application No. 61/413,828, filed Nov. 15, 2010, titled“Fiber Plugs and Adapters for Managed Connectivity,” U.S. ProvisionalApplication No. 61/437,504, filed Jan. 28, 2011, titled “Fiber Plugs andAdapters for Managed Connectivity,” and U.S. application Ser. No.13/025,841, filed Feb. 11, 2011, titled “Managed Fiber ConnectivitySystems,” the disclosures of which are hereby incorporated herein byreference in their entirety.

Additional details pertaining to some example types of coupler modules420 are disclosed in U.S. Provisional Application No. 61/303,948, filedFeb. 12, 2010, titled “Bladed Communications System,” U.S. ProvisionalApplication No. 61/413,844, filed Nov. 15, 2010, titled “CommunicationsBladed Panel Systems,” U.S. Provisional Application No. 61/439,693,filed Feb. 4, 2011, titled “Communications Bladed Panel Systems,” andU.S. application Ser. No. 13/025,750, filed Feb. 11, 2011, titled“Communications Bladed Panel Systems,” the disclosures of which arehereby incorporated herein by reference in their entirety.

Certain types of chassis housings 410 may include a back plane 415 towhich the coupler modules 420 may be communicatively (e.g.,electrically) coupled (see FIG. 10). In some implementations, the backplane 415 includes a connector port 416 for each coupler module 420. Inthe example shown, each coupler module 420 includes at least one printedcircuit board 425 that connects to the connector port 416 using acard-edge connection. In other implementations, the circuit board 425 ofeach coupler module 420 can connect to the respective port 416 using aconnectorized cable or other type of connectors.

In some implementations, the coupler modules 420 also include aprocessor 426. For example, as discussed above with respect to FIG. 2,the processor 426 of each coupler module 420 may be a slave processorthat connects to a master processor 430 (FIG. 28) through the back plane415. In some implementations, one master processor 430 controls multipleslave processors 426. In certain implementations, one master processor430 is installed on the backplane 415 and controls the slave processor426 of each coupler module 420 of the distribution module 400. In otherimplementations, one master processor 430 may control the slaveprocessors 426 of multiple distribution modules 400. In still otherimplementations, each distribution module 400 may be associated withmultiple master processors 430. In still other implementations, eachcoupler module 420 has an independent processor 426.

In accordance with some implementations, the coupler modules 420 areslideably mounted to the chassis 410. For example, in someimplementations, the coupler modules 420 can be moved between aretracted position and at least a first extended position. The couplermodule 420 is housed within the chassis 410 when in the retractedposition. At least a portion of the coupler module 420 extends from thefront of the chassis 410 when in the first extended position. Forexample, the coupler module 420 may be moved to the first extendedposition to facilitate insertion and/or removal of a connectorized end512, 514, 522 of one or more cables 510, 520 at the ports 422, 424 ofthe coupler module 420.

In certain implementations, the coupler modules 420 also can move to asecond extended position in which more of the coupler modules 420 extendfrom the chassis 410 as compared to the first extended position (e.g.,compare the three coupler modules 420 of FIG. 9). In someimplementations, the coupler modules 420 remain connected to thebackplane 415 when moved between the retracted and first extendedpositions. In certain implementations, the coupler modules 420 aredisconnected from the backplane 415 when the coupler modules 420 are inthe second extended position. For example, the coupler module 420 may bemoved to the second extended position to facilitate replacement of theprocessor 426.

In some implementations, each coupler module 420 includes one or morecable retainers 450 (FIG. 9) that manage the patch cables 510 pluggedinto the coupler modules 420. Each retainer 450 defines a channel 451through which one or more patch cables 510 may be routed. The retainerschannels 451 aid in guiding and organizing the patch cables 510 betweenthe front ports 422 and the management sections 330 of the rack 301.When the coupler modules 420 are moved to the extended positions, thefront ports 422 move forwardly relative to the rack 301 (e.g., to themanagement sections 330 of the rack 301). In certain implementations,the retainers 450 manage the patch cables 510 when the coupler modules420 are moved between the retracted and extended positions to inhibitexcessive bending of the patch cables 510 between the front ports 422and the management sections 330 of the rack 301. For example, eachretainer channel 451 has a sufficient cross-sectional area to enable thepatch cables 510 to slide within the retainer channel 451.

In some implementations, the coupler modules 420 include coupler blades,such as the coupler blades disclosed in U.S. application Ser. No.13/025,750, incorporated by reference above. In certain implementations,the couplers of the coupler blades 420 include one or more fiber opticadapters. In other implementations, the couplers of the coupler blades420 include one or more electrical jacks, punch downs, or otherelectrical connections. In still other implementations, the couplers ofthe coupler blades 420 may include both fiber optic adapters andelectrical jacks. In other implementations, the coupler modules 420 mayinclude patch panels, termination drawers, etc.

Referring to FIGS. 16-20, the distribution modules 400 are configured tobe installed at the mounting sections 320 of the rack 301 in spacedgroups 440. Each group 440 of distribution modules 400 defines onedistribution section 308 of the rack 301 (see FIG. 16). In someimplementations, the distribution sections 308 of the rack 301 arearranged in a vertically stacked arrangement (e.g., see FIGS. 4 and 6).In some such implementations, the mounting sections 320, travel sections350, and storage sections 360 are arranged in vertically stackedconfigurations (see FIGS. 4-8). In other implementations, however, thedistribution sections 308 can be arranged in other configurations (e.g.,horizontal rows, staggered rows or columns, etc.).

In some implementations, each distribution section 308 may have a heightof 2 RU. Accordingly, in one implementation, four distribution modules400, each having a height of ½ RU, may be installed at the mounting area320 of the distribution section 308. In another implementation, twodistribution modules 400, each having a height of 1 RU, may be installedat the distribution section 308. In another implementation, a singledistribution module 400 having a height of 2 RU may be installed at thedistribution section 308. In other implementations, each distributionsection 308 may have a greater or lesser height (e.g., 1 RU, 4 RU, 5 RU,8 RU, etc.).

FIGS. 16-20 show an enlarged view of a portion of the example rack 301.In the example shown, two distribution modules 400 are mounted in asingle distribution section 308. In other implementations, greater orfewer distribution modules 400 may be mounted in each distributionsection 308.

The mounting section 320 of each distribution section 308 includes atleast one mounting rail 322 to which the distribution modules 400 can bemounted. In the example shown, the mounting area 320 includes two spacedmounting rails 322. In some implementations, a unitary mounting rail 322runs vertically along the inner side of each tower 311, 313 of the rack301 from the bottom 305 to the top 304. In other implementations,separate mounting rails 322 are located at each distribution section 308or mounting section 320. A first end 403 (FIG. 10) of each distributionmodule 400 is mounted to a first of the mounting rails 322 and a secondend 404 (FIG. 10) of the distribution module 400 can be mounted to asecond of the mounting rails 322 (see FIG. 16).

In the example shown, each mounting rail 322 includes two rail arms 324extending from a rail base 326 to define a U-shaped transversecross-section (e.g., see FIGS. 5 and 17). In one implementation, therail base 326 of each mounting rail 322 attaches to the respective tower311, 313. The ends 403, 404 of the distribution modules 400 are mountedto the rail arms 324 (see FIG. 16). For example, each distributionmodule 400 may include a mounting flange 408 (FIG. 10) at either end ofthe distribution module 400. Each mounting flange 408 may be fastened toone of the rail arms 324 through one or more holes 328 (FIG. 6) definedin the rail arm 324. In the example shown, each rail arm 324 definessets of two holes 328 at which the distribution modules 400 can beinstalled.

In accordance with some aspects, the cable management structures of therack 301 may provide for separation of the cables 500 into groups thatfacilitate managing (e.g., adding, removing, deleting, organizing,and/or identifying) the cables 500. In accordance with other aspects,the cable management structures may be configured to inhibit bending ofthe cables 500 beyond a maximum bend radius. In accordance with otheraspects, the cable management structures may be configured to organizethe cables 500 to facilitate adding, removing, and rerouting cables 500within the rack system 300.

For example, as shown in FIGS. 16 and 17, each distribution section 308defines at least one management section 330 at which the patch cables510 may be organized. In the example shown, the distribution section 308defines a first management section 331 at a first side of the mountingarea 320 and a second management section 332 at a second side of themounting area 320. In other implementations, the rack 301 may definemanagement sections 330 on only one side. In some implementations, themanagement sections 330 are located at the front of the towers 311, 313.In other implementations, the management sections 330 are located at afront of the rack 301, but elsewhere on the framework 310.

Each management section 331, 332 includes one or more cable managementstructures mounted to a support plate 333 (e.g., see FIG. 17). Forexample, in some implementations, the front sides 302 of the tower 311,313 form the support plates 333 of the management sections 3131, 332,respectively. In one implementation, a single support plate 333 extendsalong all of the management sections 330 of a tower. In otherimplementations, each management section 330 has a unique support plate333 separated from the support plates 333 of the adjacent managementsections 330 (see FIG. 4).

In certain implementations, each management segment 331, 332 alsoincludes a transition surface 335 located between the support plate 333and the mounting section 320 (e.g., see FIG. 4). In accordance with someaspects, the transition surface 335 may function as a bend radiuslimiter for the patch cables 510 routed between the management sections331, 332 and the distribution modules 400. In accordance with otheraspects, routing the patch cables 510 around the transition surface 335provides slack length of the patch cables 510 to accommodate movement ofthe distribution modules 420 as will be described in more detail herein.

In certain implementations, each management section 330 includes one ormore retention fingers 334 located adjacent the transition surface 335.The retention fingers 334 define channels (e.g., generally horizontalchannels) 399 (FIG. 17) that are configured to direct patch cables 510to and from the distribution modules 400 (e.g., to and from the cableretainers 450 at the first sides 401 of the coupler modules 420). Incertain implementations, the retention fingers 334 cooperate with thecable retainers 450 to organize and/or support the patch cables 510plugged into the front ports 422 of the distribution modules 400. Insome implementations, the retention fingers 334 define slots or otheropenings 398 (FIGS. 16 and 17) through which the patch cables 510 can beinserted into and removed from the channels 399.

In some implementations, each management section 330 includes at leastone retention finger channel 399 (FIG. 17) for each distribution module400 that the distribution section 308 is configured to receive. Incertain implementations, each management section 330 includes multipleretention finger channels 399 for each distribution module 400. In oneimplementation, each management section 330 includes at least oneretention finger channel 399 for each coupler module 422 that is capableof being installed at the distribution section 308.

In some implementations, each retention finger 334 may service all ofthe patch cables 510 extending from a single one of the distributionmodules 400. In other implementations, multiple retention fingers 334may service the patch cables 510 of one distribution module 400. Forexample, each retention finger 334 may service the patch cables 510 ofone coupler module 420 of the distribution module 400. In anotherimplementation, multiple retention fingers 334 may service the patchcables 510 of one coupler module 420. In still other implementations, asingle retention finger 334 may service the patch cables 510 of multipledistribution modules 400.

Each management section 330 also includes bend radius limiters 336(FIGS. 7 and 8) that inhibit patch cables 510 from bending sufficientlyto hinder the functionality of the patch cable 510. For example, incertain implementations, each management section 330 includes a fullspool 337 and a partial spool 338 (see FIG. 23). In the example shown,the full spool 337 is located beneath the partial spool 338. In otherimplementations, the management sections 330 can have otherconfigurations of bend radius limiters 336 (e.g., the full spool on top,two or more partial spools, two or more full spools, etc.). In certainimplementations, each management section 330 also includes a plate 339mounted over at least a portion of the bend radius limiters 336 to aidin retaining the patch cables 510 in the management sections 330. In theexample shown, the plate 339 mounts over the full spool 338.

The rear 303 of the rack 301 defines one or more travel sections 350along which the patch cables 510 can be routed across the rack 301and/or to other racks in the rack system 300 (e.g., see FIGS. 18-20). Inaccordance with some aspects, the rear 303 of the rack 301 defines onetravel section 350 for each distribution section 308 (see FIG. 19). Inaccordance with other aspects, one travel section 350 can servicemultiple distribution sections 308. In accordance with still otheraspects, multiple travel sections 350 can service one distributionsection 308. In some implementations, the troughs 352 of the travelsection 350 are connected to a rear side of each tower 311, 313 forsupport. In other implementations, troughs 352 are otherwise connectedto the frame construction 310 at the rear 303 of the rack 301 (FIG. 5).

Each travel section 350 includes at least one trough 352 that extends atleast partially across the rear 303 of the rack 301. In the exampleshown, each travel section 350 has one trough 352 that extends fullyacross the rear 303 of the rack 301 and connects to each of the towers311, 313 (see FIG. 19). In certain implementations, each trough 352includes a tray 353 on which the patch cables 510 can lay and a lip 354that aids in retaining the patch cables 510 on the tray 353. In oneimplementation, the tray 353 extends generally horizontally and the lip354 extends generally vertically. In other implementations, however, thetray 353 can be angled relative to the ground to aid in retaining thepatch cables 510 or to aid in limiting the bend radius of the patchcables 510.

The sides 306, 307 of the rack define one or more storage sections 360.Each slack storage area 360 includes one or more cable storagestructures (e.g., spools, half-spools, partial-spools, or other bendradius limiters) 362 (e.g., see FIGS. 7 and 8). In the example shown inFIG. 19, the cable storage structures 362 include spools 363 that eachhave a retaining flange 364 at one end of the spool 363. The spools 363of each storage section 360 are positioned in a single column betweenside flanges 366. In other implementations, each slack storage area 360can include multiple columns of spools 363 or other radius limiters. Oneor more retainers 368 also can be positioned at the slack storagearea(s) 360 to aid in holding the patch cables 510 within the storagearea(s) 360. In the example shown, each slack storage area 360 includesone retainer 368 positioned at a bottom 305 of the rack 301.

Referring to FIG. 20, the rack 301 can include one or more cable guides370 along which various cables 500 can be routed to different sectionsof the rack 301. For example, in some implementations, the rack 301includes vertical routing channels and horizontal routing channels. Thefront 302 of the rack 301 may define one or more front vertical channels371 through which portions of the patch cables 510 can be routed toupper or lower distribution sections 308 (see FIGS. 7, 8 and 17). Therear 303 of the rack 301 may define one or more rear vertical channels372 (FIG. 20) through which at least portions of the patch cables 510,distribution cables 520, and PLI cables 530 can be routed to upper orlower distribution sections 308 as will be described in more detailherein.

In some implementations, the front vertical channels 371 are definedbetween the support plates 333 of the management sections 330 and theside flanges 366 defining the slack storage areas 360 (see FIGS. 17 and20). Retainers 378 extend between the support plates 333 and the storagearea flanges 366 to hold the patch cables 510 within the front verticalchannels 371 (see FIG. 17). In some implementations, the front verticalchannels 371 span the width of plates 333 and flange 366. In otherimplementations, the front vertical channels 371 are wider or narrowerthan the plates 333 and flange 366. At least one recess is defined inthe support plate 333 at each distribution section 308 to facilitatetransitioning the patch cables 510 from the respective front verticalchannels 371 to one of the management sections 330.

In certain types of racks 301, the rear vertical channels 372 includeone or more travel channels 373 defined between the troughs 352 of thetravel sections 350 and the storage area plates 366 of the storage area360 (see FIGS. 18, 20 and 27). For example, one or more recesses can bedefined in the trays 353 of the troughs 352 to at least partially formthe travel channels 373. In the example shown in FIG. 5, two recessesare defined on opposite sides of each tray 353 to form two travelchannels 373 (e.g., see FIG. 20). Patch cables 510 enter the travelchannels 373 from the troughs 352 via the recesses. Retainers 379 extendbetween the trays 353 and the storage area plates 366 (see FIG. 19) toaid in maintaining the patch cables 510 within the travel channels 373.

Certain types of troughs 352 include transition members 356 thatfacilitate routing the patch cables 510 between the troughs 352 and thetravel channels 373. In the example shown in FIG. 5, a transition member356 is installed at each recess on each trough 352. In someimplementations, each transition member 356 is configured to funnel oneor more of the patch cables 510 from the trough 352 to the travelchannel 373 (see FIG. 27). In the example shown, the transition member356 couples to the tray 353 and an inner lip of the trough 352 (see FIG.19).

In certain types of racks 301, the rear vertical channels 372 alsoinclude one or more distribution channels 374 (see FIGS. 18, 20, and27). In some implementations, the distribution channels 374 are formedby rails 376. In the example shown in FIG. 5, each rail 376 is generallyU-shaped. In certain implementations, each rail 376 is formed from atleast one side flange 377. Indeed, in some implementations, each rail376 includes two side flanges 377 to define the channel 374 (see FIG.17). In other implementations, each rail 376 may be a unitary piece. Inthe example shown, each rail 376 is positioned at the rear 303 of therack 301 so that each distribution channel 374 extends adjacent one ofthe travel channels 373. In other implementations, the distributionchannel(s) 374 may be separated from the travel channel(s) 373.

In certain types of racks 301, the rear vertical channels 372 alsoinclude one or more PLI routing channels 375 (see FIGS. 18, 20, and 27).Each additional routing channel 375 extends vertically between anexterior of one of the rails 376 and one of the sides 403, 404 of thedistribution modules 400 positioned on the rack 301 (see FIGS. 18, 20,and 27). In some implementations, the additional routing channels 375have a smaller cross-sectional area than the distribution channels 374,which have a smaller cross-sectional area than the travel channels 373(see FIG. 20). In other implementations, the distribution channels 374may have the largest cross-sectional area of the rear vertical channels372. In still other implementations, the rear vertical channels 372 mayhave any desired cross-sectional area.

In some implementations, one or more of the vertical channels 370connect to one of the slack storage areas 360. For example, in certainimplementations, the front vertical channels 371 and the travel channels373 connect to the storage areas 360. In certain implementations, thefront vertical channel 371 and the travel channel 373 located at thefirst side 306 of the rack 301 connect to the storage area 360 locatedat the first side 306 of the rack 301 (see FIG. 4). The front verticalchannel 371 and the travel channel 373 located at the second side 307 ofthe rack 301 connect to the storage area 360 located at the second side307 of the rack 301 (see FIG. 5). In certain implementations, thestorage sections 360 are located at the outer side of each tower 311,313. In other implementations, the distribution channels 374 also mayconnect to the storage areas 360.

In one implementation, the vertical channels 370 connect to therespective storage areas 360 at a bottom of the channels 370. Forexample, cables routed through the vertical channels 370 may be routedbeneath the plates 366 of the respective storage area 360 at the bottom305 of the rack 301. In certain implementations, the base 309 of therack 301 defines a storage trough 369 at each slack storage area 360 toaid in transitioning the patch cables 510 between the slack storage area360 and the vertical channels 371. For example, the trough 369 mayinhibit the patch cables 510 from extending onto the floor around therack 301.

As shown in FIG. 20, the top 304 of certain types of racks 301 providesaccess to at least some of the vertical channel guides 370. For example,in some implementations, at least the distribution channels 374 and thePLI routing channels 375 extend to the top 304 of the rack 301 (see FIG.17). The distribution cables 520 and/or the PLI cables 530 can betransitioned at the top 304 of the rack 301 between the channels 374,375 and one or more overhead raceways or other routing structures. Inother implementations, the base 309 of the rack 301 provides access toat least some of the cable guides 370. The distribution cables 520and/or the PLI cables 530 can be transitioned at the bottom 305 of therack 301 between the cable guides 370 and one or more floor-level orbelow-ground tracks.

In the example shown in FIG. 20, the rack 301 includes a first PLIrouting channel 375A at one side of the distribution module 400 and asecond PLI routing channel 375B at an opposite side of the distributionmodule 400. In certain implementations, one or more PLI cables 530 maybe routed down the first channel 375A and one or more grounding cablesmay be routed down the second channel 375B. In other implementations,both PLI cables 530 and grounding cables may be routed down bothchannels 375A, 375B. In still other implementations, the PLI cablesinclude grounding conductors.

Horizontal channel guides 380 extend between the front 302 of the rack301 to the rear 303 of the rack 301 to connect the management sections330 to the travel sections 350 (see FIG. 20). For example, at least onehorizontal channel guide 380 may extend between the top and bottom ofadjacent module groups 440 to connect one of the management sections 330to one of the travel sections 350 (see FIG. 17). In otherimplementations, multiple channel guides 380 may service eachdistribution section 308. For example, in one implementation, at leaston horizontal channel guide 380 may extend between each distributionmodule 400.

Each horizontal channel guide 380 includes a track or raceway 383 havingan entrance port 381 and an exit port 389 (FIGS. 24 and 25). The track383 extends between a front 302 of the rack 301 and a rear 303 of therack 301. One or more flanges 385 extend over an open top of the track383 to aid in retaining the patch cables 510 within the track 383. Theentrance port 381 of each track 383 is located at one of the managementregions 330 of the distribution section 308 The exit port 389 of eachtrack 383 is located at the troughs 352 of the distribution section 308.In certain implementations, the track 383 provides bend radiusprotection to fiber optic cables routed therein. For example, the track383 may define curves 382, 388 that ease the transition of the fibersbetween one direction and another without bending the fiber beyond amaximum limit.

FIGS. 21-28 illustrate some routing paths that may be utilized by cablesrouted to, from, and within the rack 301. In general, the distributioncables 520 are routed along the rear 303 of the rack 301 (e.g., from oneor more cable raceways) to the rear ports 424 of the distributionmodules 400. Signals carried by the distribution cables 520 plugged intothe rear ports 424 of the distribution modules 400 pass through thedistribution modules 400 to patch cables 510 plugged into the frontports 422 of the distribution modules 400.

The patch cables 510 carry the signals from the respective front ports422 to either different distribution module ports or othercommunications equipment. For example, in some implementations, anexample patch cable 510 can be routed from a front port 422 of adistribution module 400 located at a source rack 301, through acorresponding management section 330 at the front 302 of the source rack301, along a horizontal channel guide 380 toward a rear 303 of thesource rack 301, to a corresponding travel section 350 at the rear 303of the source rack 301.

In some implementations, the patch cable 510 is routed along the travelsection 350 to the travel section 350 of a destination rack. In otherimplementations, the source rack 301 is the destination rack 301. Fromthe appropriate travel section 350, the patch cable 510 is routed to astorage section 360 at one of the sides 306, 307 of the destinationrack, to a management section 330 at the front 302 of the destinationrack, to another front port 422 of the same or a different distributionmodule 400.

In accordance with certain aspects, one or more PLI cables 530 also canbe routed to the rack 301 (e.g., from one or more cable raceways). Forexample, the PLI cables 530 also may be routed along the rear 303 of therack 301 to PLI ports 428 at the rear or sides of the distributionmodules 400. In some implementations, the PLI cables 530 carry power tothe distribution modules 400 or components installed therein. In otherimplementations, the PLI cables 530 carry PLI signals between thedistribution modules 400 and a data network. Certain types of PLI cables530 can carry both power and PLI signals (e.g., have at least one powerwire and at least one communications wire).

One example routing configuration for the example rack 301 will now bedescribed in more detail with respect to FIGS. 21-28. In the examplerouting configuration, the rack 301 is configured to receive one or moredistribution cables 520 (see FIG. 21) that carry communication signals(see signals S1 of FIG. 1) to the distribution modules 400. The rack 301also is configured to receive one or more patch cables 510 that connectthe distribution modules 400 to other distribution modules 400 of therack system 300 and/or to other communications equipment. The rack 301also is configured to receive PLI cables 530 that carry PLI signals (seesignals S2 of FIG. 1) between the distribution modules 400 or masterprocessors 430 associated therewith and a data network (e.g., network218 of FIG. 2).

Referring to FIGS. 21 and 22, in some implementations, the distributioncables 520 are transitioned from an overhead raceway to an entrance ofthe distribution channel 374 at the top 304 of the rack 301. Eachdistribution cable 520 is routed through a distribution channel 374defined by a rail 376 to one of the distribution modules 400 (see FIG.21). An appropriate number of distribution cables 520 are transitionedfrom the distribution channel 374 at each distribution module 400.

For example, in FIG. 21, a first distribution cable 520A and a seconddistribution cable 520B are routed downwardly through the distributionchannel 374. The first distribution cable 520A is transitioned out ofthe distribution channel 374 at the distribution module 400 shown. Thesecond distribution cable 520B continues past the distribution module400 to a different distribution module 400 located out-of-sight in FIG.21.

In some implementations, the connectorized end 522 of the distributioncable 520A is routed to a rear port 424 at the second side 402 of thedistribution module 400 (see FIG. 22). In other implementations, eachdistribution cable 520 is routed through the second side 402 of therespective distribution module 400, over a select coupler module 420, toa rear cable ports 424 of a coupler located at the front 401 of thedistribution module 400. In such implementations, the connectorized end522 of each distribution cables 520 is interfaced directly with theconnectorized end 512 (FIG. 23) of one or more patch cables 510. Thetroughs 352 of the rack 301 are sufficiently spaced so that a user canaccess these ports 424 from the rear 303 of the rack 301.

In certain implementations, the distribution modules 400 include atleast one retention arrangement 460 at which the distribution cables 520can be secured to the second side 402 of the distribution module 400(FIGS. 21-22). For example, the distribution cables 520 may be routed tothe retention arrangement 460 before the connectorized end 522 isplugged into the rear ports 424 of the distribution module 400. In someimplementations, the retention arrangement 460 includes at least a firstretention structure located at the second side 402 of the distributionmodule chassis 410. In some implementations, the first retentionstructure includes a clamping member 462 (FIG. 22). In otherimplementations, the first retention structure includes a fan-outarrangement 466 (FIG. 20) at which individual fibers of the cables 520are separated and, optionally, upjacketed.

In certain implementations, the retention arrangement 460 also includesat least one cable tie 464 that fastens each distribution cable 520 toan appropriate coupler module 420 of the distribution module 400. Incertain implementations, the cable ties 464 are located at a rear end ofan elongated flange 465 extending rearward from the coupler module 420.The cable ties 464 are positioned so that slack length of thedistribution cables 520 routed to the coupler module 420 is providedbetween the ties 464 and the first retention structure mounted to thedistribution module chassis 410. The slack length enables the couplermodules 420 to be slid forwardly relative to the chassis 410 and rack301 without straining or disconnecting the distribution cables 520. Thecable ties 464 also may facilitate securing and/or organizing thedistribution cables 520.

In some implementations, one or more of the distribution cables 520includes multiple optical fibers that are terminated by a multi-fiberconnector (e.g., an MPO connector). In some such implementations, one ormore of the distribution cables 520 may be routed through one or moreclamping members 462, through cable ties 464, to the rear ports 424 atthe second side 402 of the distribution module 400 (e.g., see FIG. 22).In other such implementations, one or more of the distribution cables520 may be routed to one or more fan-out arrangements 466 and separatedinto individual fibers that may be routed through cable ties 464 overone or more coupler modules 420 to the rear 464 of the front couplers ofthe coupler modules 420.

In still other implementations, one or more of the distribution cables520 includes one or more optical fibers that are each terminated by asingle-fiber connector (e.g., an LC connector, SC connector, STconnector, FC connector, LX.5 connector, etc.). In some suchimplementations, one or more of the distribution cables 520 may berouted through one or more clamping members 462, through cable ties 464,to the rear ports 424 at the second side 402 of the distribution module400. In other implementations, however, other types of retentionstructures may be utilized.

In the example shown in FIG. 22, two connectorized distribution cables520 are routed through clamping members 462 to two rear cable ports 424at the second side 402 of the bottom coupler module 420 of the chassis410. In one implementation, each of the connectorized distributioncables 520 shown include multi-fiber cables terminated by an MPOconnector. In other implementations, however, each distribution cable520 may include a single optical fiber terminated by a single-fiberconnector. In still other implementations, the distribution cables 520may include electrical cables that terminate at electrical plugs (e.g.,RJ plugs), electrical jacks (e.g., RJ jacks), punch downs, wire ties, orother suitable connectors.

Referring to FIG. 23, the communication signals carried by thedistribution cables 520 pass through the distribution modules 400 to thefirst set of cable ports 422. One or more patch cables 510 carry thecommunication signals between two respective distribution module ports422 or between a distribution module port 422 and communicationsequipment. In general, each patch cable 510 extends from a firstconnectorized end 512 to a second connectorized end 514. The firstconnectorized end 512 of each patch cable 510 is plugged into one of thefront ports 422 of a distribution module 400. From the firstconnectorized end 512, each patch cable 510 is routed to a respectivemanagement section 330. The connectorized ends 512, 514 of some examplepatch cables 510 are shown in FIG. 23. For clarity and ease in viewing,the distribution module(s) 400 positioned on the rack 301 are not shownin FIG. 23.

In FIG. 23, seven patch cables 510A-510G are shown routed through theappropriate management sections 330 to different distribution sections308 of the rack 301. A first example patch cable 510A includes a firstconnectorized end 512A that is configured to be plugged into one of thefront ports 422 of a distribution module 400 located at a firstdistribution section 308A. From the first connectorized end 512A, thefirst example patch cable 510A extends to a first management region 332Alocated on the first side 306 of the rack 301. At the first managementregion 332A, the first example patch cable 510A extends over therespective transition surfaces 335, through the respective retentionfingers 334, to the bend radius limiters 336. The bend radius limiters336 route the first example patch cable 510A toward a horizontal channelguide 380A associated with the first management region 332A.

The first example patch cable 510A also includes a second connectorizedend 514A that is configured to be plugged into one of the front ports422 of a distribution module 400 located at the first distribution area308A. In some implementations, the connectorized end 514A may be pluggedinto a front port 422 of the same coupler module 420 as the firstconnectorized end 512A. In other implementations, the connectorized ends514A may be plugged into a front port 422 of a different coupler module420 of the same or a different distribution module 400. From the secondconnectorized end 514A, the first example patch cable 510A extends to afirst management region 331A located on the second side 307 of the rack301. At the first management region 331A, the first patch cable 510Aextends over the respective transition surface 335, through therespective retention fingers 334, to the bend radius limiters 336. Inthe example shown, the first patch cable 510A is routed over a partialspool 338 of the limiters 136 and into a front vertical channel 371 atthe second side 307 of the rack 301. The connection between the firstand second connectorized ends 512A, 514A will be shown with reference toFIGS. 24-27.

A second example patch cable 510B includes a first connectorized end512B that is configured to be plugged into one of the front ports 422 ofa distribution module 400 located at a second distribution area 308B.From the first connectorized end 512B, the second example patch cable510B extends to a second management region 332B located on the firstside 306 of the rack 301. At the second management region 332B, thesecond example patch cable 510B extends over the respective transitionsurfaces 335, through the respective retention fingers 334, to the bendradius limiters 336. In the example shown, the second patch cable 510Bis routed around a full spool 337 of the bend limiters 336 toward ahorizontal channel guide 380A associated with the first managementregion 332B.

The second example patch cable 510B also includes a second connectorizedend 514B that is configured to be plugged into one of the front ports422 of a distribution module 400 located at the second distribution area308B. In some implementations, the connectorized end 514B may be pluggedinto a front port 422 of the same coupler module 420 as the firstconnectorized end 512B. In other implementations, the connectorized ends514B may be plugged into a front port 422 of a different coupler module420 of the same or a different distribution module 400. From the secondconnectorized end 514B, the second example patch cable 510B extends overthe respective transition surface 335, through the respective retentionfingers 334, to the bend radius limiters 336. In the example shown, thesecond patch cable 510B is routed over a partial spool 338 of the bendlimiters 336 and into a front vertical channel 371 at the first side 306of the rack 301. The connection between the first and secondconnectorized ends 512B, 514B will be shown with reference to FIGS.24-27.

Third and fourth example patch cables 510C, 510D are shown routedthrough a second management region 331B at the second side 307 of therack 301. Each of these patch cables 510C, 510D has a firstconnectorized end 512C, 512D, respectively that is configured to beplugged into one of the front ports 422 of a distribution module 400located at the second distribution area 308B. The connectorized ends512C, 512D may be plugged into front ports 422 of the same or adifferent coupler module 420. From the connectorized ends 512C, 512D,the third and fourth patch cables 510C, 510D extend over the respectivetransition surfaces 335, through the respective retention fingers 334,to the bend radius limiters 336 of the second management region 331B atthe second side 307 of the rack 301. In the example shown, the third andfourth patch cables 510C, 510D are routed around a full spool 337 at thesecond management region 331B and into a corresponding horizontalchannel guide 380C.

The second ends of the third and fourth patch cables 510C, 510D are notshown in FIG. 23. For example, in some implementations, the second endsof the third and fourth patch cables 510C, 510D may be routed todistribution modules 400 positioned at distribution sections 308 of therack 301 that are outside the scope of FIG. 23. In otherimplementations, the second ends of the third and fourth patch cables510C, 510D may be routed to distribution modules 400 located on adifferent rack in the rack system 300 as will be described in moredetail herein.

A fifth example patch cable 510E includes a second connectorized end514E that is configured to be plugged into one of the front ports 422 ofa distribution module 400 located at the second distribution area 308B.From the second connectorized end 514E, the fifth example patch cable510E extends over the respective transition surface 335, through therespective retention fingers 334, to the bend radius limiters 336 of afirst management region 331A at the second side 307 of the rack 301. Inthe example shown, the fifth example patch cable 510E is routed over apartial spool 338 and into the front vertical channel 371 at the secondside 307 of the rack 301.

The first end of the fifth example patch cable 510E is not shown in FIG.23. For example, in some implementations, the first end of the fifthpatch cable 510E may be configured to plug into a distribution module400 positioned at a distribution section 308 of the rack 301 that isoutside the scope of FIG. 23. In other implementations, the first end ofthe fifth patch cable 510E may be routed to a distribution module 400located on a different rack in the rack system 300.

FIGS. 24 and 25 are plan views of the rack 301 with patch cables routedthrough the horizontal channel guides 380 from the management regions330 at the front 302 of the rack 301 to a travel region 350 at the rear303 of the rack 301. From the travel region 350, each patch cable 510may be routed to a travel channel 373 of the same rack 301, a travelchannel of an adjacent rack, a travel channel of a non-adjacent racklocated in the same rack system 300 (e.g., a rack positioned adjacent toan adjacent rack), or to communications equipment (e.g., a server, awall outlet, etc.). FIG. 24 shows a plan view of the first distributionsection 308A of the rack 301 and FIG. 25 shows a plan view of the seconddistribution section 308B of the rack 301. For clarity and ease inviewing, the distribution module(s) 400 positioned on the rack 301 arenot shown in FIGS. 24 and 25.

In FIG. 24, the first patch cable 510A is routed from the firstmanagement section 332A at the front 302 of the rack 301, along a firsthorizontal channel guide 380A, to a first cable trough 352A at the rear303 of the rack 301. In the example shown, the first horizontal channel380A is connected to the second tower 313. For clarity, only the portionof the first patch cable 510A that extends away from the limiters 336 isshown. The first patch cable 510A is routed along the track 383 of thechannel guide 380A from a front port 381 at the management region 332Ato a rear port 389 at the trough 152A. Retaining fingers 385 extend overthe first patch cable 510A at spaced intervals to aid in holding thefirst patch cable 510A within the track 383.

At the rear port 389 of the horizontal channel 380, the first patchcable 510A is transitioned onto the first trough 352A. In general, thefirst patch cables 510A can be transitioned from the exit port 389towards either the first side 306 of the rack 301 or the second side 307of the rack 301. In the example shown, the first patch cable 510A istransitioned towards the second side 307 of the rack 301 to one of thetransition members 356. The transition member 356 aids in transitioningthe first patch cable 510A from the trough 352 to one of the travelchannels 373 at the rear 303 of the rack 301.

In other implementations, the first patch cable 510A may be routed pastthe travel channel 373 at the second side 307 of the rack 301 to atrough 352 of an adjacent rack (see dotted line 510A′ of FIG. 24). Inother implementations, the first patch cable 510A may be routed to adifferent travel channel 373 at the first side 306 of the rack 301 (seedotted line 510A″ of FIG. 24). In still other implementations, the firstpatch cable 510A may be routed past the other travel channel 373 at thefirst side 306 of the rack 301 to a trough 352 of another adjacent rack(see dotted line 510A′ of FIG. 24).

In certain implementations, the troughs 352 of adjacent racks 301 alignwith each other. Accordingly, patch cables 510 may be routed from thehorizontal channel exit ports 389, along the troughs 352 of source racks301, to the troughs 352 of destination racks, to appropriate travelchannels 373 at the destination racks. In certain implementations, oneor more additional racks 301 may be located between the source rack andthe destination rack. In other implementations, the source rack anddestination rack are the same rack.

For example, in some implementations, the patch cables 510 includeintra-rack patch cables 510 that have a first common length andinter-rack patch cables 510 that may come in one of many standardlengths. For example, the length may vary depending on how many racksthe patch cable 510 is expected to span. In other implementations, patchcables 510 having different lengths may be utilized. In still anotherimplementation, patch cables 510 all having a common length may beutilized. In certain implementations, the patch cables 510 have a commonlength ranging from about one meter to about twenty meters. Indeed, incertain implementations, the patch cables 510 have a common lengthranging from about two meters to about ten meters. In one exampleimplementation, each patch cable 510 configured to span one rack 301 isabout six meters long.

In FIG. 25, the second, third, and fourth patch cable 510B-510D arerouted from the management section 332A, 332B at the front 302 of therack 301, along first and second horizontal channel guides 380B, 380C,to a second cable trough 352B at the rear 303 of the rack 301. In theexample shown, the horizontal channel 380B is connected to the secondtower 313 and the horizontal channel 380A is connected to the firsttower 3111. For clarity, only the portions of the patch cables 510B-510Dthat extend away from the limiters 336 are shown.

The second patch cable 510B is routed along the track 383 of the channelguide 380B from a front port 381 at the management region 332B to a rearport 389 at the trough 352B. Retaining fingers 385 extend over thesecond patch cable 510B at spaced intervals to aid in holding the secondpatch cable 510B within the track 383. At the rear port 389 of thehorizontal channel 380B, the second patch cable 510B is transitionedonto the second trough 352B. In the example shown, the second patchcable 510B is transitioned towards the first side 306 of the rack 301 toone of the transition members 356. The transition member 356 aids intransitioning the second patch cable 510B from the trough 352B to one ofthe travel channels 373 at the rear 303 of the rack 301.

The third and fourth patch cables 510C, 510D are routed along the track383 of a channel guide 380C from a front port 381 at the managementregion 331B to a rear port 389 at the second trough 352B. Retainingfingers 385 extend over the patch cables 510C, 510D at spaced intervalsto aid in holding the patch cables within the track 383. At the rearport 389 of the horizontal channel 380C, the third patch cable 510C istransitioned onto the second trough 352B, towards the first side 307 ofthe rack 301, to one of the transition members 356. The transitionmember 356 aids in transitioning the third patch cable 510C from thesecond trough 352B to one of the travel channels 373 at the rear 303 ofthe rack 301. At the rear port 389 of the horizontal channel 380C, thefourth patch cable 510D is transitioned onto the second trough 352B,towards the first side 307 of the rack 301, to a trough of an adjacentrack.

The fifth patch cable 510E is shown being transitioned onto the secondtrough 352B from a trough of a rack that is located adjacent the secondside 307 of the rack 301. In the example shown, the fifth patch cable510E is routed to the transition member 356 at the second side 307 ofthe rack 301 and transitioned into a travel channel 373. In otherimplementations, the fifth patch cable 510E may be routed across thesecond trough 352B to the transition member 356 at the first side 306 ofthe rack 301 or to a trough of another rack that is located adjacent thefirst side 306 of the rack 301.

As shown in FIG. 20, in certain implementations, each travel channel 373may be divided into a first portion 373 a and a second portion 373 b.The first portion 373 a of the channel 373 is defined by the funnelportion of each transition member 356. The second portion 373 b of thechannel 373 is defined by the outer surfaces of the transition member356 and the retaining fingers 379. In such implementations, patch cables510 entering the travel channel 373 are routed from one of thetransition members 356 into the first portion 373 a of the channel 373.The patch cables 510 are transitioned from the first portion 373 a tothe second portion 373 b as they progress through the channel 373 toallow additional patch cables 510 to be transitioned into the firstportion 373 a at a subsequent (e.g., lower) trough 352 (e.g., see FIG.27).

Referring to FIG. 26, the patch cables 510 are routed from the travelchannels 373 at the rear 303 of a destination rack 301, through a slackstorage region 360, to one of the distribution sections 308 at the front302 of the destination rack 301. In FIG. 26, a first representativepatch cable 510G is routed through the travel channel 373 from a trough352 out of view of FIG. 20. The second example patch cable 510B also isvisible in FIG. 26 being transitioned from the second trough 352B to thetravel channel 373. Both of the patch cables 510G, 510B are routed downthe travel channel 373 to the storage trough 369 located at the base 309of the rack 301.

At the trough 369, the patch cables 510G, 510B are wrapped around thesecond side 307 of the rack 301 to one of the front vertical channel371. Each of the patch cables 510G, 510B is routed up the front verticalchannel 371 to the management section 330 of an appropriate distributionsection 308. For example, the second example patch cable 510B is routedup the front vertical channel 371 to a management section 330 out ofview of FIG. 26. As shown in FIG. 23, the second patch cable 510B istransitioned from the front vertical channel 371 to the managementsection 332B of the second distribution section 308B by routing thepatch cable 510B between the support plate 333 and the cover plate 339of the management section 332B. The second patch cable 510B is woundabout the half spool 338B at the management region 332B and directedthrough one of the retention fingers 334. The second connectorized end514B is plugged into one of the ports 410 of a distribution module 400mounted at the second distribution section 308B.

The first representative patch cable 510G is transitioned from the frontvertical channel 371 to the management section 330 of the bottomdistribution section 308 by routing the patch cable 510 between thesupport plate 333 and the cover plate 339 of the management section 330(see FIG. 26). As discussed above, the first representative patch cable510G can be wound about one or more of the limiters 336 at themanagement region 330 and directed through one of the retention fingers134 towards the distribution section 308. The second connectorized endof the first representative patch cable 510G can be plugged into one ofthe ports 410 of a distribution module 400 mounted at the distributionsection 308.

In some implementations, when patch cables 510 are routed across thestorage trough 369, a slack length of the patch cables 510 is left atthe side 306, 307 of the rack 301, but not yet transitioned into theslack storage area 360. In such implementations, the slack length isstored at the spools 363 of the storage area 360 after the secondconnectorized ends 514 of the patch cables 510 have been routed to theappropriate distribution sections 308. In other implementations, theslack length of the patch cables 510 is routed through the slack storagearea 360 before transitioning the patch cables 510 to the front verticalchannels 371 of the rack 301.

As further shown in FIG. 26, the patch cables 510 may be transitionedinto the slack storage area 360 beneath the retainer 368. Each patchcable 510 is wrapped about one of the spools 363 of the slack storagearea 360 in a half-loop configuration. The spool 363 about which theslack length is wrapped depends on the amount of slack length to betaken up. In the example shown, the excess length of the second patchcable 510B is wrapped around the third spool 363 from the storage trough369 and the first representative patch cable 510G is wrapped around thesecond spool 363 from the storage trough 369.

In certain implementations, the second connectorized ends 514 of one ormore of the patch cables 510 may be disconnected from the front ports422 and reconnected to different front ports 422 at the same or adifferent coupler module 420. If the second connectorized ends 514 arereconnected to front ports 422 at a different distribution section 308,then the slack length of the patch cables 510 may need to be adjusted.For example, the slack length may be looped around a higher or lowerspool 363 at the slack storage area 360.

Referring now to FIGS. 27 and 28, in accordance with some aspects, PLIcables 530 can be routed to PLI ports 428 at the distribution modules400. In some implementations, the PLI cables 530 are transitioned fromone or more raceways or other routing structures to one or more of thePLI routing channels 375 (FIGS. 20 and 27) of the rack 301. From the PLIrouting channels 375, the PLI cables 530 can be routed to an appropriatedistribution module 400 (e.g., to a side or rear of the distributionmodule 400). In other implementations, however, the PLI cables 530 canbe routed along the distribution channels 374 instead of along separatechannels 375.

As shown in FIG. 27, in some implementations, the PLI cables 530 areconfigured to plug into PLI ports 428 (e.g., power connection ports, USBports, electrical ports, and/or physical layer management ports) of thedistribution modules 400. In one implementation, the PLI port 428 isformed on the master processor 430 associated with the distributionmodule 400 (see FIG. 28). In another implementation, the PLI port 428 isformed on the back plane 415 of each distribution module 400. In stillother implementations, each coupler module 420 within the distributionmodule 400 defines a PLI port 428.

In some implementations, the PLI cables 530 are configured to carrypower to the distribution modules 400. In other implementations, the PLIcables 530 are configured to carry PLI signals (e.g., signals S2 of FIG.1). In certain implementations, the PLI cables 530 electrically connectto the back plane 415 of a distribution module 400 to connect thedistribution module 400 to a data network (e.g., network 101 of FIG. 1,network 218 of FIG. 2, etc.). In certain implementations, physical layerinformation (e.g., pertaining to the distribution cables 520, patchcables 510, coupler modules 420, the distribution module 400, etc.) iscarried by the PLI cables 530 between the distribution modules 400 andthe data network.

Referring to FIGS. 29 and 30, the management regions 330 manage thepatch cables 510 when one or more coupler modules 420 are moved relativeto the chassis 410 of the distribution modules 400. For example, in someimplementations, the distribution modules 400 are mounted to the rack301 so that the front ports 422 are located at positions recessed fromthe front 302 of the rack 301 (e.g., see FIGS. 29-30). The retentionfingers 334 and transition surfaces 335 of the management regions 330and the retaining members 450 of the coupler modules 420 cooperate tomanage bending of the patch cables 510 during movement of the couplermodules 420 between the retracted position and at least the firstextended position.

The front ports 422 of each coupler modules 420 are configured to travelover a distance D1 when the coupler module 420 moves between theretracted position and the first extended position. In someimplementations, the distance D1 ranges from about one inch to about sixinches. Indeed, in some implementations, the distance D1 ranges fromabout two inches to about five inches. In one example implementation,the distance D1 is about three inches. In another exampleimplementation, the distance D1 is about four inches.

The front ports 422 of each coupler modules 420 are configured to travelover a distance D2 when the coupler module 420 moves between theretracted position and the second extended position. In someimplementations, the distance D2 ranges from about two inches to aboutten inches. Indeed, in some implementations, the distance D2 ranges fromabout four inches to about eight inches. In one example implementation,the distance D2 is about five inches. In another example implementation,the distance D2 is about six inches. In another example implementation,the distance D2 is about seven inches.

Patch cables 510 plugged into front ports 422 of distribution modules400 mounted to a rack 301 extend forwardly from the front ports 422 andsideways into the retainer members 450 of the respective coupler module420. From the retaining member 450, the patch cables 510 extend towardthe transition surfaces 335 of a respective management region 330. Incertain implementations, patch cables 510 plugged into the front ports422 at one side of the distribution module 400 extend towards themanagement regions 332 at the first side 306 of the rack 301 and patchcables 510 plugged into the front ports at another side of thedistribution module 400 extend toward the management regions 331 at thesecond side 307 of the rack 301. At the respective management regions330, the patch cables 510 follow the transition surfaces 335 forwardlyand sideways toward the respective retention fingers 334. The patchcables 510 are routed through channels defined by the appropriateretention fingers 334 and forwarded to the bend radius limiters 336.

When one or more of the coupler modules 420 is moved (e.g., pulled)forwardly to the first extended position (e.g., see first ports 422′represented by a dashed line in FIG. 29), slack length of thecorresponding patch cables 510 unbends at least partially from thetransition surfaces 335 (see patch cable 510′ shown as a dotted line inFIG. 29) to accommodate the movement. However, the patch cables 510remain held by the retaining fingers 334 and retaining members 450. Theretention fingers 334 extend sufficiently forward of the rack 301 toprovide ample cross-sectional space in which the patch cables 510 canmove (see FIG. 30) to accommodate movement of the first connectorizedends 512 with the coupler modules 420. Accordingly, movement of thecoupler modules 420 to at least the first extended position does notplace strain on the patch cables 510. Further, the patch cables 510remain organized and managed throughout the movement between theretracted and extended positions.

In some implementations, the retention fingers 334 provide sufficientroom for the patch cables 510 to move away from the transition surfaces335 without exceeding a maximum bend radius when the coupler modules 420are moved to the second extended position (e.g., see first ports 422″represented by a second dashed line in FIG. 29). In otherimplementations, however, the patch cables 510 are disconnected from acoupler module 420 before the coupler module 420 is moved to the secondextended position. For example, the patch cables 510 may be disengagedfrom the retention fingers 334 through slots 398 to accommodate themovement of the coupler module 420.

In accordance with some aspects of the disclosure, a process for storingslack patch cable length in a rack system including at least a firstrack includes plugging a first connectorized end of a first patch cableat a first front port positioned at the first rack; routing the firstpatch cable forwardly and sideways from the first front port, over atransition surface, to a front of the first rack to provide a firstslack length of the first cable at the front of the first rack; androuting the first patch cable sideways through a retention fingertowards a first management section located at the front of the firstrack at which the first patch cable is routed around a bend radiuslimiter and into a horizontal channel. The process also includes routingthe first patch cable through the horizontal channel from the front ofthe first rack, beneath the first front port, to a rear of the firstrack; routing the first patch cable over a trough located at the rear ofthe first rack towards a first travel channel located at a rear of adestination rack at which the first patch cable is routed downwardly toa bottom, rear of the destination rack; and routing the first patchcable from the bottom, rear of the destination rack, around one side ofthe destination rack, to a bottom, front of the destination rackincluding leaving a second slack length of the first cable at the sideof the destination rack. The process also may include routing the firstpatch cable upwardly from the bottom, front of the destination rack to adestination management section at which the first patch cable is wrappedat least partially around a bend radius limiter; routing the first patchcable from the destination management section, sideways through a secondretention finger, and rearward and sideways over a second transitionsurface to a second front port positioned at the destination rack; andplugging a second connectorized end of the first patch cable at thesecond front port positioned at the destination rack.

In some implementations, the process for storing slack patch cablelength also includes moving the first coupler module forwardly to theextended position while the connectorized end of the first patch cableremains in the first front port; removing the connectorized end of thefirst patch cable from the first front port while the first couplermodule is in the extended position; plugging a connectorized end of asecond patch cable into the first front port while the first couplermodule is in the extended position; and moving the first coupler modulerearward to the retracted position with the connectorized end of thesecond patch cable in the first front port. In one exampleimplementation, the first coupler module is moved forwardly about threeinches.

In some implementations, the process for storing slack patch cablelength also includes removing the additional patch cables from theretention fingers at the front of the first rack; and moving the firstcoupler module to a second extended position while the connectorizedends of the additional patch cables remain plugged into the front portsof the first coupler module, the second extended position being locatedforwardly of the first extended position. In one example implementation,the first coupler module is moved forwardly about six inches.

In accordance with some implementations, a process for coupling at leastone distribution cable to at least one patch cable at a first rackincludes routing a distribution cable vertically along a rear of thefirst rack to a coupler module; moving the first coupler moduleforwardly to an extended position; accessing a connectorized end of thefirst distribution cable from the front of the first rack and pluggingthe connectorized end of the first distribution cable into a first rearport from the front of the first rack while the first coupler module isin the extended position. The process also may include moving the firstcoupler module rearward to a retracted position; and plugging aconnectorized end of the patch cable into a first front port of thecoupler module.

In some implementations, the process also includes moving the firstcoupler module to the extended position without unplugging theconnectorized end of the distribution cable from the first rear port;removing the connectorized end of the patch cable from the first frontport; plugging a connectorized end of a second patch cable into thefirst front port; and moving the first coupler module to the retractedposition.

The above specification, examples and data provide a completedescription of the manufacture and use of the composition of theinvention. Since many embodiments of the invention can be made withoutdeparting from the spirit and scope of the invention, the inventionresides in the claims hereinafter appended.

1. (canceled)
 2. A rack having a front, a rear, a top, a bottom, a firstside, and a second side, the rack comprising: a plurality of reartroughs at the rear of the rack; a plurality of front-facing portsmounted to the rack at a location intermediate the front and rear, thefront-facing ports being configured to move horizontally relative to therack between a retracted position and an extended position that isforward of the retracted position, the front-facing ports beingseparated into groups with each group being associated with one of therear troughs; a first plurality of bend radius limiters located at thefront of the rack, each bend radius limiter being associated with one ofthe groups of front-facing ports; a plurality of horizontal channelslocated on the rack, each horizontal channel extending between one ofthe bend radius limiters at the front of the rack and one of the reartroughs at the rear of the rack; and a storage area located at the firstside of the rack, the storage area including a plurality of managementspools.
 2. The rack of claim 2, wherein the front ports are moved aboutthree inches between the retracted and extended positions.
 3. The rackof claim 2, wherein the front ports are configured to move to a secondextended position that is farther forward relative to the rack than thefirst extended position.
 4. The rack of claim 3, wherein the front portsare moved about six inches between the retracted position and the secondextended position.
 5. The rack of claim 2, wherein the front ports arepositioned on a plurality of distribution modules mounted on the rack.6. The rack of claim 5, wherein each distribution module includes acoupler module that is moveable relative to the distribution module,thereby moving the front ports between the retracted and extendedpositions.
 7. The rack of claim 5, wherein the distribution modules aredisposed in a central column on the rack.
 8. The rack of claim 2,wherein the management spools of the storage area are disposed in acolumn.
 9. The rack of claim 8, wherein the column spans a majority of aheight of the rack.
 10. The rack of claim 2, wherein the plurality ofbend radius limiters includes a first group of bend radius limiters anda second group of bend radius limiters, the first group of bend radiuslimiters being located at the front of the rack to a first side of thefront ports, the second group of bend radius limiters being located atthe front of the rack to a second side of the front ports.
 11. The rackof claim 10, wherein the plurality of horizontal channels includes afirst group of horizontal channels and a second group of horizontalchannels, the first group of horizontal channels extending betweenrespective rear troughs and respective bend radius limiters of the firstgroup of bend radius limiters, and the second group of horizontalchannels extending between respective rear troughs and respective bendradius limiters of the second group of bend radius limiters.
 12. Therack of claim 11, wherein the horizontal channels of the first group ofhorizontal channels are laterally aligned with the horizontal channelsof the second group of horizontal channels.
 13. The rack of claim 2,wherein the storage area is a first storage area, and wherein the rackfurther comprises a second storage area located at the second side ofthe rack, the storage area including a plurality of management spools.14. The rack of claim 2, further comprising a front vertical channelspanning a height of the rack.
 15. The rack of claim 14, furthercomprising a rear vertical channel spanning a height of the rack. 16.The rack of claim 2, further comprising a rear vertical channel spanninga height of the rack.
 17. The rack of claim 16, wherein the rearvertical channel is a first rear vertical channel, and wherein the rackfurther comprises a second rear vertical channel.
 18. The rack of claim17, wherein the first rear vertical channel is defined by a plurality ofretaining fingers.
 19. The rack of claim 17, wherein the first rearvertical channel is defined by a unitary rail.
 20. The rack of claim 2,wherein open ends of the horizontal channels face the respective bendradius limiters.
 21. The rack of claim 2, further comprising first andsecond columns of retention fingers disposed at the front of the rack,the first column of retention fingers being disposed at a first side ofthe front ports and the second column of retention fingers beingdisposed at a second side of the front ports.